AppSec Blog

AppSec Blog

The Day the World Will End

With a new movie coming out about how the world will end with the (supposed) end of the Mayan calender in 2012, I figured it would be nice to get a list of software related "end of calender" issues:

Dec. 31st 1999, 23:59:59 GMT
The famous Y2k issue. We made it... (so far ;-) )

Jan. 10th, 2010, 10:10:00 GMT
"Binary Armageddon Day". The binary representation, 1010011010 translates to '666'. Also, the date only includes 1s and 0s (other then the '2' in the year). (thx Gadi. Also see Gadi's facebook group about this issue ). If you are on facebook, you can find the group here: Gadi's Binary Armageddon Day Facebook Group.

Dec. 21, 2012
end of Mayan calendar. Just listed here because everybody is talking about it. Should not affect software (other then the fact that the world will end that day).

Feb. 7th 2036, 6:28:16 GMT
The last date that can be expressed using "ntp". ntp is a protocol used to synchronize clocks on the internet. The ntp date starts on Jan 1st 1900 and is expressed in 64 bits. The first 32 bits are used to indicate the number of seconds since Jan 1st 1900, the remaining bits are used as fractional seconds.

Jan. 19th 2038, 03:14:07 GMT
The end of the Unix epoch. Unix uses a 32 it signed number to express time. '0' is January 1st 1970. The last date that can be expressed using unix time is Jan 19th 2038. After that... who knows? This can already be a problem. Imagine you are a bank and handing out 30 year mortgages?

Dec. 31st 9999, 23:59:59 GMT
The end of 4 digit years. Well, we got a while until that will happen.

Got any other dates of note? Let us know!