Bug ID: JDK-8179614 Test for jarsigner on verifying jars that are signed and timestamped by other JDK releases

JDK-8179614 : Test for jarsigner on verifying jars that are signed and timestamped by other JDK releases

Type: Bug
Component: security-libs
Sub-Component: java.security
Affected Version: 9

Priority: P3
Status: Resolved
Resolution: Fixed

Submitted: 2017-05-04
Updated: 2017-08-18
Resolved: 2017-08-16

Versions (Unresolved/Resolved/Fixed)

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.

JDK 10
10 b20Fixed

Related Reports

Relates :	JDK-7102686 - Restructure timestamp code so that jars and modules can more easily share the same code
Relates :	JDK-6776954 - The JARSigner does not correctly interpret failure information of a trusted timestamp service
Relates :	JDK-8177674 - Change JDK 6 jarsigner -tsadigestalg default to SHA-256
Relates :	JDK-8038837 - Add support to jarsigner for specifying timestamp hash algorithm
Relates :	JDK-8049480 - Current versions of Java can't verify jars signed and timestamped with Java 9

Description

A jarsigner in a JDK release should verify a jar that is signed and timestamped by other JDK releases.

Comments

Code review: http://mail.openjdk.java.net/pipermail/security-dev/2017-June/015943.html

06-06-2017