[I'm resending this because I don't think it got out the last time]
>Yes, SSLeay is y2k safe. The only place this could affect things is in the
>certificate code and I do allow for 01 == 2001. The only other thing that is
>a problem is the unix time == seconds since 1970. This will overflow in
>2037(?) and as such and certificates to be signed greater than this will stuff
>up. I am looking at fixing this.
Are you still using a 100-year window since 1970 for the switchover? I seem to
recall seeing that a long time ago, you should really switch over in 2050
rather than 2070.
As for > 2038 certs, these do exist. MS in their infinite wisdom give certs
generated with their MakeCert utility a default validity of (get ready for
this) 40 years(!!). However MakeCert's certs are otherwise so comprehensively
broken that I don't know if it's worth bothering even trying to read them.
Peter.
+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/ |
+-------------------------------------------------------------------------+
