Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
NullPointerException is thrown by java-17-openjdk package in FIPS mode if NSSDB contains DSA key.
Steps to reproduce using ssl-tests[1]:
cd ssl-tests
git checkout 446e6f8801b80d65499abe32ce7e77614b14e926
make clean && make TEST_PKCS11_FIPS=1 SSLTESTS_CUSTOM_JAVA_PARAMS=-Djdk.tls.ephemeralDHKeySize=2048
...
Exception in thread "main" java.lang.NullPointerException: Cannot invoke "java.security.interfaces.DSAParams.getP()" because "params" is null
at jdk.crypto.cryptoki/sun.security.pkcs11.P11DSAKeyFactory.implTranslatePublicKey(P11DSAKeyFactory.java:57)
at jdk.crypto.cryptoki/sun.security.pkcs11.P11DSAKeyFactory.engineGeneratePublic(P11DSAKeyFactory.java:109)
at java.base/java.security.KeyFactory.generatePublic(KeyFactory.java:351)
at java.base/sun.security.x509.X509Key.buildX509Key(X509Key.java:224)
at java.base/sun.security.x509.X509Key.parse(X509Key.java:171)
at java.base/sun.security.x509.CertificateX509Key.<init>(CertificateX509Key.java:75)
at java.base/sun.security.x509.X509CertInfo.parse(X509CertInfo.java:674)
at java.base/sun.security.x509.X509CertInfo.<init>(X509CertInfo.java:169)
at java.base/sun.security.x509.X509CertImpl.parse(X509CertImpl.java:1791)
at java.base/sun.security.x509.X509CertImpl.<init>(X509CertImpl.java:183)
at java.base/sun.security.provider.X509Factory.engineGenerateCertificate(X509Factory.java:105)
at java.base/java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:355)
at jdk.crypto.cryptoki/sun.security.pkcs11.P11KeyStore.loadCert(P11KeyStore.java:1195)
at jdk.crypto.cryptoki/sun.security.pkcs11.P11KeyStore.mapLabels(P11KeyStore.java:2359)
at jdk.crypto.cryptoki/sun.security.pkcs11.P11KeyStore.engineLoad(P11KeyStore.java:771)
at java.base/java.security.KeyStore.load(KeyStore.java:1473)
at SSLSocketTester.loadKeystore(SSLSocketTester.java:151)
at SSLSocketTester.getKeyManagers(SSLSocketTester.java:123)
at SSLSocketTester.init(SSLSocketTester.java:89)
at Main.main(Main.java:29)
Openjdk build:
java-17-openjdk-devel-17.0.0.0.33-0.5.ea.el8
Additional info:
This was introduced by patch, which disables non-fips crypto from SUN and SunEC providers [2].
[1] https://github.com/zzambers/ssl-tests
[2] http://pkgs.devel.redhat.com/cgit/rpms/java-17-openjdk/commit/?h=rhel-8.5.0&id=526f27daaeed6c737f91315386efa5ab368696a6
Comment 6RHEL Program Management
2023-03-21 07:27:50 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.