-
Bug
-
Resolution: Fixed
-
P4
-
7u51, 8
-
None
-
b124
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8218527 | openjdk8u212 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8213683 | 8u202 | Ivan Gerasimov | P4 | Resolved | Fixed | b04 |
JDK-8211964 | 8u201 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8216909 | emb-8u201 | Ivan Gerasimov | P4 | Resolved | Fixed | master |
JDK-8220299 | 7u231 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8219290 | openjdk7u | Ivan Gerasimov | P4 | Resolved | Fixed | master |
"This jar contains signatures that does not include a timestamp. Without a timestamp, users may not be able to validate this jar after the signer certificate's expiration date (%1$tY-%1$tm-%1$td) or after any future revocation date."
The phrase "signatures that does not" is grammatically incorrect. I suggest changing this to:
"This jar contains one or more signatures that do not include a timestamp. Without a timestamp, ..."
Also, if there is more than one signature that is not timestamped, just listing the expiration date of one of the certificates is misleading and confusing, since there may be other signer certs. I can't think of a very good way to address this though. It would probably be too verbose to list the expiration date of each certificate.
- backported by
-
JDK-8211964 New jarsigner timestamp warning is grammatically incorrect
- Resolved
-
JDK-8213683 New jarsigner timestamp warning is grammatically incorrect
- Resolved
-
JDK-8216909 New jarsigner timestamp warning is grammatically incorrect
- Resolved
-
JDK-8218527 New jarsigner timestamp warning is grammatically incorrect
- Resolved
-
JDK-8219290 New jarsigner timestamp warning is grammatically incorrect
- Resolved
-
JDK-8220299 New jarsigner timestamp warning is grammatically incorrect
- Resolved
- relates to
-
JDK-8159805 sun/security/tools/jarsigner/warnings/NoTimestampTest.java fails after JDK-8027781
- Resolved