title: Signed java applet no longer works in any browser if I set the clock ahead on my computer
body: <p>I have a Java Applet (for a browser) signed and timestamped with a valid Code Signing Certificate from GoDaddy.  The code signing certificate itself expires in a few weeks.  Everything I've read says that the applet will still be valid after the Code Signing Certificate expires: </p>
  
  <p>From <a href="https://www.digicert.com/code-signing/java-7-update-51-code-signatures-required.htm" rel="noreferrer">here</a>:</p>
  
  <blockquote>
    <p>If a timestamp is discovered, then the code signature is valid until the end of time, as long as the code remains unchanged</p>
  </blockquote>
  
  <p>I would like to verify this is actually true though.  If I change my computer's clock settings to a later date, past when the certificate expires, I get the following Java Exception in IE, Firefox and Chrome:</p>
  
  <blockquote>
    <p>java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Response is unreliable: its validity interval is out-of-date</p>
  </blockquote>
  
  <p>Does this mean that the applet will actually fail in a few weeks when the Code Signing Certificate expires, or is this test of changing my computer clock just invalid?  Any references either way?</p>