update README.md: fixing incompatibility with Java #205
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
The example of RSA-OAEP encryption/decryption with SHA-256 and MGF1 padding is now compatible with Java (with the BC provider), as stated in the comment
|
I believe that there's an incompatibility between the BC provider and SunJCE in this case. The README should actually be updated to show how to use both and indicate which example to use with which provider. The original example works with SunJCE (at least I believe it was SunJCE that was used originally), and I assume your example works with BC. Sorry for the slow response! |
|
I happened to stumble over this thread while looking at JCE/BC interop issues -- they are compatible but JCE requires some extra parameters -- see the updated BC thread. Just FYI. |
davidlehn
added a commit
that referenced
this pull request
Jan 5, 2022
- Add examples for a compatibility issue. - See #205.
|
Sorry, this got auto-closed due to branch rename. See #936. |
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.
Hi,
The example of RSA-OAEP encryption/decryption with SHA-256 and MGF1-SHA1 is not compatible with Java's RSA/ECB/OAEPWithSHA-256AndMGF1Padding (although this is claimed in the commend), at least for the BC provider (I have not checked it with any other providers).
When changed to MGF1-SHA256, it becomes compatible with RSA/ECB/OAEPWithSHA-256AndMGF1Padding (with BC), as claimed.