Skip to content
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

Add additional checks to NativeECDHKeyAgreement to match upstream #754

Merged
merged 1 commit into from
May 27, 2024

Conversation

KostasTsiounis
Copy link
Contributor

There are additional checks that are required during the init and doPhase parts of ECDH key agreement. Those checks are already present in the original ECDHKeyAgreement class, so they had to be added to the NativeECDHKeyAgreement class as well.

Back-ported from: ibmruntimes/openj9-openjdk-jdk#788

Signed-off by: Kostas Tsiounis kostas.tsiounis@ibm.com

@KostasTsiounis
Copy link
Contributor Author

FYI @keithc-ca

@keithc-ca
Copy link
Member

Jenkins test sanity alinux jdk8

@keithc-ca
Copy link
Member

Grinders:

Please assess the failures in jdk_security3.

@KostasTsiounis
Copy link
Contributor Author

The TestEC one is a known issue (see eclipse-openj9/openj9#19479). I have the fix for that and you should see a PR soon.

The other one doesn't seem ECDH related. Maybe we should open another issue for that.

@keithc-ca
Copy link
Member

Grinder for jdk_security3 passed with the nightly build: https://openj9-jenkins.osuosl.org/job/Grinder/3627.

@KostasTsiounis
Copy link
Contributor Author

It seems to be machine depended. It doesn't fail everywhere apparently.

@keithc-ca
Copy link
Member

Grinder for jdk_security3 passed in https://openj9-jenkins.osuosl.org/job/Grinder/3628 (running on the same machine as used by https://openj9-jenkins.osuosl.org/job/Grinder/3627).

@keithc-ca keithc-ca merged commit d5a8e3b into ibmruntimes:openj9 May 27, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants