Re: does ASN1_UTCTIME_get() changes by local time zone settings
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.
On 1/30/06, David Schwartz <email@example.com> wrote:[color=blue]
> > 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 ?[/color]
> You may encounter certificates *today* that expire in 2045 or even=[/color]
> OpenSSL Project [url]http://www.openssl.org[/url]
> Development Mailing List [email]firstname.lastname@example.org[/email]
> Automated List Manager [email]email@example.com[/email]
OpenSSL Project [url]http://www.openssl.org[/url]
Development Mailing List [email]firstname.lastname@example.org[/email]
Automated List Manager [email]email@example.com[/email]