JDK-8154005 : Add algorithm constraint that specifies the restriction date
- Type: Enhancement
- Component: security-libs
- Sub-Component: java.security
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2016-04-11
- Updated: 2017-05-17
- Resolved: 2016-05-26
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 |
|---|---|
8u152Fixed  |
9 b121Fixed |
Related Reports
|
Blocks :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Extend the jdk.certpath.disabledAlgorithms property to support a constraint that specifies the date a restriction goes into affect. The proposed name for the constraint is "denyAfter". This constraint allows us to better implement a phased approach to disabling an algorithm, and also gives administrators more control over when the restrictions will take affect.
Comments
|