Hi Bob..
On 17/10/2015 17:16, Robert Hanson wrote:
Ah, but there is a catch. Despite the fact that the Jmol code was
signed with a timestamp, revocation *prior to the expiration date of
the certificate* results in Oracle's Java applet initializer to
disregard the timestamp and not allow such applets to start. Ever again.
Ahah. I see - yet another of the intricacies of code signing. I guess
the idea here is that revoking the cert before its normal end of life
indicates code that is in some way malicious - thanks for finding out
this gem of byzantine logic ! Something to bear in mind for anyone
releasing signed code.
Jim.
------------------------------------------------------------------------------
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
