RFE 4500302 actually requests several enhancements in various places: JDK, jarsigner, PlugIn and Web Start. There is another rfe (4523234) tracking
work needed in JDK to support timestamped signatures.
We plan to implement rfe 4523234 for Tiger (pending Tiger team approval, etc.).
Once rfe 4523234 is done, PlugIn should consider time-of-signing when verifying signed jar.
So I'm filing this rfe to track the work needed in PlugIn (if any). I'll file another rfe to track work needed in Web Start (if any). RFE 4500302 will be used to track enhancements needed in jarsigner. I'll add notes in rfe 4500302.
work needed in JDK to support timestamped signatures.
We plan to implement rfe 4523234 for Tiger (pending Tiger team approval, etc.).
Once rfe 4523234 is done, PlugIn should consider time-of-signing when verifying signed jar.
So I'm filing this rfe to track the work needed in PlugIn (if any). I'll file another rfe to track work needed in Web Start (if any). RFE 4500302 will be used to track enhancements needed in jarsigner. I'll add notes in rfe 4500302.
- duplicates
-
JDK-4938222 REGRESSION: VMInfo Applet fails to load, throws AccessControlException
- Closed
-
JDK-4731841 Verisign Model Inconsistant w/ Enterprise Deployment Scenarios
- Closed
-
JDK-4485741 Signed Jar should still work after Certificate Expires
- Closed
- relates to
-
JDK-4649703 Web Start should consider time-of-signing when verifying signed jars
- Resolved
-
JDK-4500302 Verification of signed jars does not consider time-of-signing.
- Resolved
-
JDK-4523234 Timestamped Signatures
- Resolved
(1 relates to)