#y2038

Considering the real time clock on the Asspull IIIx runs at an offset from the host's reported time and defaults to January 1 1984 (you're supposed to reset it), and considering this is the only 64-bit register on the system... I wonder if that's worth the effort?

GCC actually has to pull in some extra support routines just to let the time functions handle such a large value.

If I make its time_t 32-bit it'll cut its range, but it'll look more contemporary and simplifies the compiled code.

So if your local ATM or transport service still uses Windows XP, expect some severe problems come 2038 if they don’t plan on ever upgrading their technology.

Fix #MillenniumBug or #y2038 Bug in #LInux #Perl

Millennium Bug or y2038 Bug in Unix Machine

This post is dedicated to backend programmers mainly and especially who are involved with *nix machine(s) or Macintosh as well. It is similar to Y2K only where in many older machines, the year 2000 was treated as it starts from 1900 again. This time it is with all 32 bit (4 byte) Unix machines. It can store upto 231 i.e 2147483647. If you try to find…

Chop off more SSLv2 tentacles and start fixing and noting y2038 issues. APIs that pass times as longs will have to change at some point... Bump major on both libcrypto and libssl.

ok tedu@

— guenther

http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/src/ssl/s3_enc.c.diff?r1=1.22;r2=1.23

http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/src/ssl/ssl.h.diff?r1=1.31;r2=1.32

http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/src/ssl/ssl_asn1.c.diff?r1=1.22;r2=1.23

http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/src/ssl/ssl_lib.c.diff?r1=1.37;r2=1.38

http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/src/ssl/ssl_sess.c.diff?r1=1.23;r2=1.24

http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/src/ssl/ssl_txt.c.diff?r1=1.14;r2=1.15