[Messenger] Support signing messages per handler #62230
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HypeMC
approved these changes
Oct 31, 2025
src/Symfony/Bundle/FrameworkBundle/Resources/config/messenger.php
Outdated
Show resolved
Hide resolved
nicolas-grekas
added
the
❄️ Feature Freeze
nicolas-grekas
force-pushed
the
msg-sign
branch
from
c5f33ef to
21c5ac5
Compare
fabpot
approved these changes
Nov 1, 2025
Member
|
Thank you @nicolas-grekas. |
This was referenced Nov 2, 2025
Merged
Merged
Contributor
|
@nicolas-grekas Can I ask how will this behave if I have an existing queue with messages and then enable this in production? Will those existing messages not be processed as they are missing the signature? What is the recommended way to enable this in production for existing queues? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment, if one is able to inject a forged payload into a queue, one can trigger any handler via the messenger consumer, including eg
RunProcessHandler. This is not a security issue in Symfony itself because queues should be protected from arbitrary payload injection. But it'd still be nice to harden this.This PR adds a new
signattribute to themessenger.message_handlerDI tag (which can be set either via explicit config or via#[AsMessageHandler]).When at least one handler does so, a
SigningSerializerdecorator is added to all transport serializers. This then computes the signature when encoding a message bound to such handlers, and verifies it when decoding one.The
signattribute is enabled forRunProcessHandlerandRunCommandHandler, and can be for any others of yours.Submitting for 7.4 as having a hardened LTS looks important to me.