JDK-8156684 : Release Note: SunPKCS11 Provider no longer offering SecureRandom by default
  • Type: Sub-task
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 8u112,9
  • Priority: P4
  • Status: Closed
  • Resolution: Delivered
  • Submitted: 2016-05-10
  • Updated: 2022-06-14
  • Resolved: 2016-06-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8u112Resolved
Description
SecureRandom.PKCS11 from the SunPKCS11 Provider is disabled by default on Solaris because the native PKCS11 implementation has poor performance and is not recommended. If your application requires SecureRandom.PKCS11, you can re-enable it by removing "SecureRandom" from the disabledMechanisms list in conf/security/sunpkcs11-solaris.cfg

Performance improvements have also been made in the java.security.SecureRandom class. Improvements in the JDK implementation has allowed for synchronization to be removed from the java.security.SecureRandom.nextBytes(byte[] bytes) method.
Comments
The Release Notes text has been updated.
19-09-2016
Should "...you can re-enable it by changing the removing "SecureRandom" from the disabledMechanisms list" in the description be "...you can re-enable it by removing "SecureRandom" from the disabledMechanisms list"?
16-09-2016