Feature: RSA OAEP with SHA512 #330
Merged
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
leocavalcante
approved these changes
Mar 1, 2024
|
@leocavalcante do you have any plans on releasing this in a new version? I would love this feature. |
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 PR is intended to provide a helper for RSA with OAEP encoding and SHA512 digest. This will improve the security of some projects.
Side notes:
I could not find the correct latest branch in GitHub, since the version tag 5.0.3 seems to be ahead of the branch name 5.x. If the branch is ahead, sync the main branch for further community contributions.
I would suggest some information in the RSA encryption discouraging the usage of PKCS1 and OAEP with SHA1, as stated by OWASP as not secure: