Implement "Header Protection for Cryptographically Protected Email" #7386
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
iequidoo
force-pushed
the
iequidoo/use-em-dash-after-subject
branch
from
51b2395 to
9bc2aee
Compare
iequidoo
force-pushed
the
iequidoo/header-protection
branch
from
4264ed2 to
23c0d0a
Compare
iequidoo
force-pushed
the
iequidoo/header-protection
branch
2 times, most recently
from
c5ff81e to
ff46db6
Compare
iequidoo
force-pushed
the
iequidoo/header-protection
branch
3 times, most recently
from
a187251 to
12621ac
Compare
iequidoo
force-pushed
the
iequidoo/header-protection
branch
from
12621ac to
be769cd
Compare
link2xt
reviewed
Nov 11, 2025
This comment was marked as resolved.
This comment was marked as resolved.
link2xt
reviewed
Nov 11, 2025
link2xt
reviewed
Nov 11, 2025
iequidoo
force-pushed
the
iequidoo/header-protection
branch
2 times, most recently
from
4b44365 to
b083abb
Compare
…7130) This is a part of implementation of https://www.rfc-editor.org/rfc/rfc9788 "Header Protection for Cryptographically Protected Email".
Implement 4.5.3.2 of https://www.rfc-editor.org/rfc/rfc9788 "Header Protection for Cryptographically Protected Email".
iequidoo
force-pushed
the
iequidoo/header-protection
branch
from
b083abb to
125d413
Compare
…defined in RFC 9788) (#7130) And enable it by default as the standard Header Protection is backward-compatible. Also this tests extra IMF header removal when a message has standard Header Protection since now we can send such messages.
Implement 4.5.3.3 of https://www.rfc-editor.org/rfc/rfc9788 "Header Protection for Cryptographically Protected Email".
iequidoo
force-pushed
the
iequidoo/header-protection
branch
from
125d413 to
3398068
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This implements the most important parts of https://www.rfc-editor.org/rfc/rfc9788.html. Need to recheck if anything else needs implementation.
Close #7130