JDK-8030823 : Security Providers need to have their version numbers updated for JDK9
- Type: Bug
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2013-12-19
- Updated: 2015-07-07
- Resolved: 2014-01-07
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 9 |
|---|
9 b01Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Similar to JDK-7122707 In additional, all presigned jar files in jdk/make/closed/tools/crypto should be recreated so they have the right Specification-Version number. (Not sure if the policy files will need an update. The existing JDK 8 ones do not have the Specification/Implementation versions, but they were built before the switch to the new build infra.
Comments
|