Hi, > How does openssl address this problem? Is there a patch so that it does > not set the expiration date beyond the 2038 wrap around time?
We just experienced exactly the same problem, and would be happy if it got solved by OpenSSL. There is a workaround available for this specific problem: openssl ca -in CSR.csr -batch -enddate 400102030405Z The biggest Problem with the Y2038 problem I see is that most people believe that it will go away due to the migration to 64 Bit machines. But this isn't going to happen. We have to start fixing 2038 now, also for all our 32 Bit platforms, 16 Bit platforms and 8 Bit platforms. Best regards, Philipp Gühring ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
