Hide Forgot
Hi Fraser, Could you help with the test instructions for this bug? A few scenarios I have in mind are: 1. Modify KRA CS.cfg with the following kra.allowEncDecrypt.archival=true kra.allowEncDecrypt.recovery=true 2. Enable only TLS/AES ciphers in server.xml all subsystem instances. 3. Execute pki pkcs12 clis successfully. 4. Enable server-side keygen on TPS with the above KRA. Format/Enroll SCP03 v7 smartcards (this card uses AES for encryption and decryption) when the following params in TKS are set tks.defKeySet.prot3.devKeyType=AES tks.defKeySet.prot3.divers=none tks.defKeySet.prot3.diversVer1Keys=none tks.defKeySet.prot3.masterKeyType=AES tks.defKeySet.nistSP800-108KdfOnKeyVersion=00 tks.defKeySet.nistSP800-108KdfUseCuidAsKdd=true These tests would be done with certificates on HSM and FIPS enabled environment. Let me know if the above testing would be a good coverage for this bug.
Moving the NEED_INFO to the ON_QA bug https://bugzilla.redhat.com/show_bug.cgi?id=1490494
[root@nocp1 pki-kra-Dec6]# rpm -qi jss Name : jss Version : 4.4.0 Release : 10.el7 Architecture: x86_64 Install Date: Tue 28 Nov 2017 02:30:31 PM EST Group : System Environment/Libraries Size : 1029659 License : MPLv1.1 or GPLv2+ or LGPLv2+ Signature : RSA/SHA256, Wed 01 Nov 2017 02:37:50 PM EDT, Key ID 199e2f91fd431d51 Source RPM : jss-4.4.0-10.el7.src.rpm Build Date : Wed 01 Nov 2017 02:19:14 PM EDT Build Host : x86-020.build.eng.bos.redhat.com Relocations : (not relocatable) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Vendor : Red Hat, Inc. URL : http://www.mozilla.org/projects/security/pki/jss/ Summary : Java Security Services (JSS) Verifications as explained in https://bugzilla.redhat.com/show_bug.cgi?id=1490494#c12. pk12util and pki pkcs12-import tools imported the key successfully
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0958