Y2K

To the best of our knowledge and the extent of testing that we and our customers have performed, we believe that all of our tools are Y2K safe. Other than as noted below, we do not write code that interprets date strings, and where the OS tools support it, we always present 4 digit years.

We have no plans to do formal Y2K testing, if you are concerned, you are advised to do your own testing.

X.509

All of our SSL based tools use X.509 certificates. Unfortunately the X.509 spec uses a 2 digit year. We make no claims for the Y2K safety of the SSL implementation(s) you might be using, but can say that we have clients who have successfully tested SSLr* built with SSLeay-0.9.0b.

The only time that libsslfd ever cares about an X.509 date (other than testing wether one is less than or greater than another) is when it warns that a certificate will expire within 30 days. It uses the standard (for X.509 certs) pivot value of 50 to correctly display the expiry date.

mktime.pl

mktime.pl is a perl(1) module for converting date strings to seconds since the unix epoch.

This is probably the only other piece of code we distribute that ever attempts to interpret a 2 digit year value (it prefers a 4 digit year). It uses a pivot value of:

(current_year + 30) % 100