On Thu, Dec 10, 1998, Dave Finnegan wrote:
> Is mod_ssl Y2K compliant?
Although I dislike those rhetorical cross-posted questions ;-), here is the
statement I'll add to the mod_ssl FAQ after I've not crawled through the code:
| Yes, mod_ssl is Year 2000 compliant.
|
| Because first mod_ssl internally never stores years as two digits. Instead it
| always uses the ANSI C & POSIX numerical data type time_t type, which on
| mostly all Unix platforms at the moment is a signed long (usually 32-bits)
| representing seconds since epoch of January 1st, 1970, 00:00 UTC. This signed
| value overflows in early January 2038 and not in the year 2000. Second, date
| and time presentations (for instance the variable ``%{TIME_YEAR}'') are done
| with full year value instead of abbreviating to two digits.
|
| Additionally according to a Year 2000 statement from the Apache Group, the
| Apache webserver is Year 2000 compliant, too. But whether SSLeay or the
| underlaying Operating System (either a Unix or Win32 platform) is Year 2000
| compliant is a different question which cannot be answered here.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
