Explicitly configure sequester to use SHA1 for RSA OAEP #6885
Conversation
This file contains 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
FirelightFlagboy
force-pushed
the
explicit-sha1-sequester
branch
from
253a564 to
bd3be6d
Compare
Rework the code to directly use `PKey` instead of `Rsa` for the internal data.
FirelightFlagboy
force-pushed
the
explicit-sha1-sequester
branch
from
bd3be6d to
7d675b1
Compare
|
superseded by #6886 |
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.
Rework the code to directly use
PKeyinstead ofRsafor the internal data.Using
PKeyallow to configure a{De,En}crypterwith the given key.Then we can configure explicitly the padding using in the new instance