Re: And DCO too {was- [Fed-Talk] AKO/DKO and Safari 4 (UNCLASSIFIED)
Re: And DCO too {was- [Fed-Talk] AKO/DKO and Safari 4 (UNCLASSIFIED)
- Subject: Re: And DCO too {was- [Fed-Talk] AKO/DKO and Safari 4 (UNCLASSIFIED)
- From: "Timothy J. Miller" <email@hidden>
- Date: Mon, 15 Jun 2009 07:39:43 -0500
Beck, Keith M CDR ACNO NGEN, OPNAV N099 wrote:
-The Java applet was signed with a code signing certificate that isn't
in your (or anyone's chain of trust).
-The Java applet has an expired signature (20 Oct 2008).
These don't really matter. Code signing is a special case with its own
trust semantics; it works by direct trust, not by chaining or validity
periods. Otherwise you'd have an instant DoS any time a publisher cert
expired, which would lead to lawsuits. :)
Even if you signed into the DCO portal with your CAC, currently DCO asks
for your user name and password for an individual meeting anyway.
That's a cookie sharing problem, I believe.
-- Tim
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden