JDK-8184229 : Release Note: jarsigner treats timestamped signed jar invalid after the signer cert expires
- Type: Sub-task
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 7u211,8u191,9
- Priority: P4
- Status: Closed
- Resolution: Delivered
- Submitted: 2017-07-12
- Updated: 2022-12-23
- Resolved: 2017-07-15
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 |
|---|
9Resolved  |
Description
If a jar file was signed with a timestamp when the signer certificate was still valid, it should be valid even after the signer certificate expires. However, jarsigner will incorrectly show a warning that that signer's certificate chain is not validated. This will be fixed in a future release.