-
Notifications
You must be signed in to change notification settings - Fork 20
Restrict RSA paddings allowed through OpenJCEPlusFIPS #1036
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
Open
KostasTsiounis
wants to merge
2
commits into
IBM:main
Choose a base branch
from
KostasTsiounis:oaep_fips
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+64
−24
Conversation
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
c7f6ce8 to
f20e802
Compare
taoliult
reviewed
Dec 19, 2025
taoliult
approved these changes
Dec 19, 2025
Collaborator
taoliult
left a comment
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.
LGTM
jasonkatonica
requested changes
Jan 6, 2026
src/main/java/com/ibm/crypto/plus/provider/OpenJCEPlusFIPS.java
Outdated
Show resolved
Hide resolved
This change adds attributes in the RSA service registration in the OpenJCEPlusFIPS provider to only support OAEP paddings. It, also, update the engineSetPadding() method to only allow OAEP paddings to be set when the FIPS provider is used. Tests are updated accordingly to skip invalid padding tests when running with OpenJCEPlusFIPS. A temporary flag that allows the use of other paddings with OpenJCEPlusFIPS is introduced to facilitate migration of users utilizing the previous behaviour. The flag to be set to revert this behaviour is -Dcom.ibm.openjceplusfips.allowNonOAEP=true. Signed-off-by: Kostas Tsiounis <[email protected]>
f20e802 to
429e28d
Compare
jasonkatonica
approved these changes
Jan 9, 2026
Member
jasonkatonica
left a comment
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.
LGTM
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 change adds attributes in the RSA service registration in the
OpenJCEPlusFIPSprovider to only support OAEP paddings.It, also, update the
engineSetPadding()method to only allow OAEP paddings to be set when the FIPS provider is used.Tests are updated accordingly to skip invalid padding tests when running with
OpenJCEPlusFIPS.A temporary flag that allows the use of other paddings with
OpenJCEPlusFIPSis introduced to facilitate migration of users utilizing the previous behaviour. The flag to be set to revert this behaviour is-Dcom.ibm.openjceplusfips.allowNonOAEP=true.Signed-off-by: Kostas Tsiounis [email protected]