JDK-8040668 : Automate Securitypack.jar creation
- Type: Bug
- Component: deploy
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2014-04-16
- Updated: 2014-07-29
- Resolved: 2014-06-10
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 | JDK 9 |
|---|---|
8u20 b19Fixed  |
9Fixed |
Description
After JDK-8037795 baseline, dynamic blacklist and blacklisted certs info is packed inside signed jar. Need to ensure that security team and Release Engineering could create and post it with each release (and possibly between releases when new blacklist entries are needed).
Comments
|