Add SHA3 support to RSA crypto APIs - #66
Closed
jls5177 wants to merge 3 commits into
Closed
Conversation
SHA3 is not yet supported by most HSM solutions and probably wont be for a few more years. This change adds a hybrid solution that performs the EMSA-PSS and RSAES-OAEP encoding/decoding schemes in software and uses the HSM for raw encryption/decryption support. This allows the keys to continue to be protected by the HSM but still have access to newer hash algorithms.
Native RSA currently does not support SHA3 hash algorithms. This change skips the SHA3 tests when performing the native unit tests.
Contributor
Author
|
Closing this PR in favor of the older PR #44 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adding SHA3 support to RSA crypto APIs. Since most PKCS#11 libraries don't support SHA3 yet I added a Hybrid solution that performs the PSS encoding in software and then just uses plain encryption on the digest.
I've tested this on both SoftHSM and Thales HSMs and have not seen any issues.