feat: do not consider encrypting to the primary key #6779
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
link2xt
force-pushed
the
link2xt/no-primary-key-encryption
branch
from
c24aa79 to
0e3f7b7
Compare
Hocuri
approved these changes
Apr 7, 2025
Primary key is usually used for certification. It is possible to make a certification- and encryption- capable key with RSA, but RFC 9580 says that implementations SHOULD NOT generate RSA keys.
link2xt
force-pushed
the
link2xt/no-primary-key-encryption
branch
from
0e3f7b7 to
d5fc85b
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.
Primary key is usually used for certification.
It is possible to make a certification- and encryption- capable key with RSA, but RFC 9580 says
that implementations SHOULD NOT generate RSA keys.