Re: Expired certificate
- From: "Brian Komar" <brian.komar@xxxxxxxxxxxxxxxxx>
- Date: Mon, 1 Oct 2007 15:47:29 -0500
AMEN!!!
Thanks for bringing this point up
Brian
"Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:uIK%23YkFBIHA.4160@xxxxxxxxxxxxxxxxxxxxxxx
BTW, it is also worth pointing out that putting a timestamp on your signed code can help deal with some of the issues of expired certificates. The whole point of a timestamp is to provide some sort of validation of when the code was signed so that if the signing cert expires but the timestamp was within the validity period of the certificate, the client can still treat the signature on the code as valid.
Of course, this doesn't help with the existing assets if they weren't timestamped, but since you are going to have to resign everything anyway, make sure you DO apply a timestamp this time around. :)
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Brian Komar" <brian.komar@xxxxxxxxxxxxxxxxx> wrote in message news:ueBwQZEBIHA.3848@xxxxxxxxxxxxxxxxxxxxxxxThere really is nothing you can do, as you can only renew with the same key pair during the validity period of the certificate.
Once you miss the date, you are toast.
This sounds like it is signed by a commercial provider, so setting back the clocks is not an option
Time to get signing
Brian
.
- Follow-Ups:
- Re: Expired certificate
- From: Solboy
- Re: Expired certificate
- References:
- Expired certificate
- From: Solboy
- Re: Expired certificate
- From: Brian Komar
- Re: Expired certificate
- From: Joe Kaplan
- Expired certificate
- Prev by Date: Re: NTBU error
- Next by Date: Re: remote desktop issues
- Previous by thread: Re: Expired certificate
- Next by thread: Re: Expired certificate
- Index(es):
Relevant Pages
|