We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/sanity/tahrir/blob/master/src/main/java/tahrir/io/crypto/TrCrypto.java RSA/None/NoPadding can only be used securely if no padding is required: If if the size of the plaintext is a multiple of the block-size... In encrypt() it is... but not in encryptRaw() ! In any case, you might want to either have padding OR to introduce a check ;)
OAEP is state of the art; something like "RSA/None/OAEPWithSHA512AndMGF1Padding" would work nicely.
The text was updated successfully, but these errors were encountered:
Would adding padding complicate serializing RSAPublicKey?
Sorry, something went wrong.
No, I think it will only affect the encrypted data, not the key itself.
On Tue, Mar 12, 2013 at 1:12 PM, Kieran Donegan [email protected]:
Would adding padding complicate serializing RSAPublicKey? — Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-14792919 .
— Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-14792919 .
Ian Clarke Blog: http://blog.locut.us/
Needs some additional research, hold off on this one
sanity
No branches or pull requests
https://github.com/sanity/tahrir/blob/master/src/main/java/tahrir/io/crypto/TrCrypto.java
RSA/None/NoPadding can only be used securely if no padding is required:
If if the size of the plaintext is a multiple of the block-size... In
encrypt() it is... but not in encryptRaw() ! In any case, you might want
to either have padding OR to introduce a check ;)
OAEP is state of the art; something like
"RSA/None/OAEPWithSHA512AndMGF1Padding" would work nicely.
The text was updated successfully, but these errors were encountered: