I will not get certificates today for after 2045 because the certificates that I am checking are certificates that already past a validation check and have been inserted into my cache system, therefor it is a certificate signed by our own system which does not sign for more then 25 year. most are 1 year.
Thanks Joe On 1/30/06, David Schwartz <[EMAIL PROTECTED]> wrote: > > > My mistake it was ASN1_TIME that is correct. > > > > But any way, I don't see a reason why I should not be able to convert > > it, if I don't care for milliseconds, time_t can represent times for > > up to 2038, so It should be ok to convert it to the time_t. > > > > Any ideas, the ASN1_cmp_time does much more than what I need, because > > I will be comparing at least once a second (If I check the last time > > to be at least one second earlier.) And because they are all in my > > cache for hopefully lets say a year, why not convert it to time_t and > > just check it with > current_gmt_time ? > > You may encounter certificates *today* that expire in 2045 or even > later. > > DS > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
