JDK-7122707 : Security Providers need to have their version numbers updated for JDK8
- Type: Bug
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 8
- Priority: P2
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-12-19
- Updated: 2015-07-07
- Resolved: 2013-09-30
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.
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 |
|---|
8 b112Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
All of the JDK security providers are supposed to have provider numbers updated for each release. It's not always done.
protected SunJSSE() {
super("SunJSSE", 1.7d, info);
These are all candidates.
sun.security.pkcs11.SunPKCS11
sun.security.provider.Sun
sun.security.rsa.SunRsaSign
sun.security.ec.SunEC
com.sun.net.ssl.internal.ssl.Provider
com.sun.crypto.provider.SunJCE
sun.security.jgss.SunProvider
com.sun.security.sasl.Provider
org.jcp.xml.dsig.internal.dom.XMLDSigRI // maybe not this one.
sun.security.smartcardio.SunPCSC
sun.security.mscapi.SunMSCAPI
Comments
|