You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mailer.rst gets a new "PGP/MIME Signing and Encryption" section: requirements (the gpg binary and the Process component, no OpenSSL extension), the warning that only the body is protected while Subject, From and To stay in cleartext, standalone usage of PgpSigner/PgpEncrypter, the global pgp_signer/pgp_encrypter configuration, the X-Pgp-Sign/X-Pgp-Encrypt headers that select the messages to protect (sign-then-encrypt, after templates are rendered and before logging), the three on_missing_key modes with the envelope.recipients caveat, and encrypt_for_sender/hide_recipients.
reference/configuration/framework.rst gets the full reference for both configuration nodes.
Thanks for documenting this, as the author of the feature I am happy to see it covered so thoroughly.
One inaccuracy worth fixing:
Unlike S/MIME, PGP/MIME is not applied to every message
That is true of the S/MIME signer, but not of the S/MIME encrypter: SmimeEncryptedMessageListener has always required the X-SMime-Encrypt header too, it just was not documented. Something like "Unlike the S/MIME signer, PGP/MIME is not applied to every message" would avoid the confusion.
For the record, I opened #22764 to document the S/MIME side (#22719), which includes that X-SMime-Encrypt header, the new certificates, on_missing_certificate and encrypt_for_sender options and the listener priorities. It touches the same part of mailer.rst and framework.rst, so whichever gets merged first, the other will need a rebase. Happy to do it on my side.
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
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.
Documents the PGP/MIME support added in symfony/symfony#64540.
mailer.rstgets a new "PGP/MIME Signing and Encryption" section: requirements (thegpgbinary and the Process component, no OpenSSL extension), the warning that only the body is protected whileSubject,FromandTostay in cleartext, standalone usage ofPgpSigner/PgpEncrypter, the globalpgp_signer/pgp_encrypterconfiguration, theX-Pgp-Sign/X-Pgp-Encryptheaders that select the messages to protect (sign-then-encrypt, after templates are rendered and before logging), the threeon_missing_keymodes with theenvelope.recipientscaveat, andencrypt_for_sender/hide_recipients.reference/configuration/framework.rstgets the full reference for both configuration nodes.Fixes #22726