-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encrypt/Decrypt/Sign/Verify using RSA in Transit backend #3489
Merged
Merged
Changes from 17 commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
3ea2ec7
encrypt/decrypt/sign/verify RSA
vishalnayak 27594aa
update path-help and doc
vishalnayak 0e105a3
Fix the bug which was breaking convergent encryption
vishalnayak e284bb8
support both 2048 and 4096
vishalnayak ce1962c
update doc to contain both 2048 and 4096
vishalnayak 9ea5196
Add test for encrypt, decrypt and rotate on RSA keys
vishalnayak 4acd786
Support exporting RSA keys
vishalnayak ea8e327
Add sign and verify test steps
vishalnayak fd65824
Remove 'RSA' from PEM header
vishalnayak 8f5b192
use the default salt length
vishalnayak a42b5b5
Add 'RSA' to PEM header since openssl is expecting that
vishalnayak 7bb366b
export rsa keys as signing-key as well
vishalnayak c0921f8
Comment the reasoning behind the PEM headers
vishalnayak 0d5ce93
remove comment
vishalnayak 174f6d7
update comment
vishalnayak f245daf
Parameterize hashing for RSA signing and verification
vishalnayak d5f001f
Added test steps to check hash algo choice for RSA sign/verify
vishalnayak e0f2dcf
Merge branch 'master-oss' into encrypt-rsa
vishalnayak 3f0fd68
fix test by using 'prehashed'
vishalnayak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC this actually depends on the format. For PKCS1 yes, but PKCS8 I believe should just be PRIVATE KEY because the type is encoded into the binary block. Might be worth mentioning that in the comment for the future as Go 1.10 will have PKCS8 encoding support and we will be adding it to PKI in this release.