-
Notifications
You must be signed in to change notification settings - Fork 720
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
jdk_security3_0_FAILED sun/security/tools/keytool/fakegen/DefaultSignatureAlgorithm.java keytool error: java.lang.UnsupportedOperationException #18320
Comments
JDK11 ppc64le_linux(
|
JDK11 ppc64le_linux(
50x grinder - 10/50 failed all in Also occurred at JDK11 s390x_linux( |
@jasonkatonica we need some help to determine what the problem is. If it's a problem with the machines we should get them updated so the test can pass. |
JDK11 aarch64_linux(
|
Normally, when we use keytool to generate keypairs, the native code from openssl will be loaded and used at first. If the native code is not satisfied, then the jave implementation will be used.
I run the Therefore, this is not a blocking issue, this could be a machine issue. |
Created infrastructure/issues/9147 |
@JinhangZhang Why do you refer to that file as "patched"? The file Did you mean to refer instead to |
Keytool command inside DefaultSignatureAlgorithm.java file use
|
This patch eliminates the 192-bit EC test which causes exceptions seen in issue #18320. DefaultSignatureAlgorithm test was run in those Redhat OS based machines in a non-FIPS mode, but with a FIPS version of openssl. So, a 192-bit size of EC key pair generator is not allowed by the native code in a FIPS version of openssl. The code path went to a replacement EC key-pair generator Java implementation. issue: eclipse-openj9/openj9#18320
Failure link
From an internal build(
rhel8-aarch64-3
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - failed at
rhel8-aarch64-6
, might be a machine setup issueThe text was updated successfully, but these errors were encountered: