RSA signature verification: Avoid wasteful key re-serialization. #1790
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.
When we added
rsa::PublicKey
we changed thering::signature
RSA implementation to construct anrsa::PublicKey
and then verify the signature using it. Unfortunately for backward compatibility with old uses ofRsaKeyPair
,rsa::PublicKey
constructor constructs (and allocates) a copy of the ASN.1-serialized public key. This is not acceptable for users who are usingring::signature
to verify a single signature. RefactorPublicKey
so that it can be bypassed by thering::signature
implementation.This is a step towards implementing allocation-free RSA signature verification.