You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some security tests consistently failed on test-ibmcloud-ubuntu1604-x64-1 but instead of an infrastructure issue it might just be a test issue, which has not be enhanced to work for those machines.
HmacPBESHA1
HmacPBESHA224 ()
HmacPBESHA256 ()
HmacPBESHA384 ()
HmacPBESHA512 ()
(*) Note: neither the current PKCS #11 standard (v3.0) nor the previous one (v2.40) define mechanisms for these algorithms. Until a future revision of the standard introduces these mechanisms, NSS vendor-specific constants will be used. Thus, non-NSS tokens will probably not support these algorithms.
The text was updated successfully, but these errors were encountered:
Some security tests consistently failed on test-ibmcloud-ubuntu1604-x64-1 but instead of an infrastructure issue it might just be a test issue, which has not be enhanced to work for those machines.
sun/security/pkcs11/KeyStore/CertChainRemoval.java.CertChainRemoval
sun/security/pkcs11/KeyStore/ImportKeyToP12.java.ImportKeyToP12
sun/security/pkcs11/Mac/PBAMac.java.PBAMac
sun/security/pkcs11/SecretKeyFactory/TestPBKD.java.TestPBKD
Except of CertChainRemoval.java all others failed with 'java.security.NoSuchAlgorithmException: no such algorithm: HmacPBESHA224 for provider SunPKCS11-NSS'
rerun on a former passed machine https://ci.adoptium.net/job/Grinder/7538/ passed
rerun on failed machine test-ibmcloud-ubuntu1604-x64-1 https://ci.adoptium.net/job/Grinder/7539/: Failed.
Action: difference between test-ibmcloud-ubuntu1604-x64-1 and others.
Also note in https://bugs.openjdk.org/browse/JDK-8301553, it mentioned:
PKCS #12 General Method for Password Integrity
HmacPBESHA1
HmacPBESHA224 ()
HmacPBESHA256 ()
HmacPBESHA384 ()
HmacPBESHA512 ()
(*) Note: neither the current PKCS #11 standard (v3.0) nor the previous one (v2.40) define mechanisms for these algorithms. Until a future revision of the standard introduces these mechanisms, NSS vendor-specific constants will be used. Thus, non-NSS tokens will probably not support these algorithms.
The text was updated successfully, but these errors were encountered: