Y2¿Que?

And there I was, 10 years ago, thinking I was wasting my time, and now this?

While the title suggests that this only effect spcific sites and companies, note who was effected:

The reports are the latest to involve the inability of computers to properly handle the 2010 date. Just after midnight on New Year's Day, Symantec's Endpoint Protection Manager stopped accepting updates after it was hit by its own 2010 date bug. Soon after the first of the year, SpamAssassin began blocking huge amounts of legitimate email because they included the 2010 in their headers, a date so far off the spam filter assumed they had to be junk.
Kaspersky software also experienced massive update problems on December 30, according to support forums, but it's not clear the new year had anything to do with them.

This is troubling in many ways:

• Have we not learned the lessons from Y2K
• With the move to cloud computing, what would be the effect of such a bug on cloud hosted applications, sevices and hosts

This is also interesting, as the only effects I was exposed to of Y2K were a delay in some Australian airport and strange document dates on Sun's documentations server. Of the ~250 systems I was in charge of at the time, only one was effected, and that one was found and repaired prior to the change of the century.