JDK-8154015 : Apply algorithm constraints to timestamped code
- Type: Enhancement
- Component: security-libs
- Sub-Component: java.security
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2016-04-11
- Updated: 2018-02-08
- Resolved: 2016-07-05
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 6 | JDK 7 | JDK 8 | JDK 9 |
|---|---|---|---|
| 6u151Resolved | 7u141Resolved | 8u131Resolved  |
9 b127Fixed |
Related Reports
|
Blocks :
|
|
|
Blocks :
|
|
|
Relates :
|
Description
Code that is timestamped before a certain date may need to be treated differently for restricted algorithms. For example, code that was timestamped before an algorithm was considered too weak to use may still be acceptable. When enforcing restrictions, we should check if the certificate's EKU includes code signing and also check if the timestamp is before or after a certain date.
Comments
|