-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 8
-
Component/s: security-libs
-
b12
-
generic
-
generic
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8163048 | openjdk7u | Sean Mullan | P4 | Resolved | Fixed | master |
Project jigsaw has added support for signed module files, which like jars, allow the user to timestamp the signed code. While developing
signed modules, it became clear that some of the current timestamping code should be restructured so that it could be more easily shared
by the 2 mechanisms (signed modules and jars).
The changes in this CR include:
1) Adding a new java.security.debug=ts option for timestamping debugging
2) Moved SignatureFileVerifier.getTimestamp() to SignerInfo.getTimestamp()
3) Moved code from TimestampedSigner to a PKCS7.generateSignedData() method
4) Other misc. small changes
signed modules, it became clear that some of the current timestamping code should be restructured so that it could be more easily shared
by the 2 mechanisms (signed modules and jars).
The changes in this CR include:
1) Adding a new java.security.debug=ts option for timestamping debugging
2) Moved SignatureFileVerifier.getTimestamp() to SignerInfo.getTimestamp()
3) Moved code from TimestampedSigner to a PKCS7.generateSignedData() method
4) Other misc. small changes
- backported by
-
JDK-8163048 Restructure timestamp code so that jars and modules can more easily share the same code
-
- Resolved
-
- duplicates
-
JDK-6776954 The JARSigner does not correctly interpret failure information of a trusted timestamp service
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Resolved
-