...@securecoding.org [mailto:sc-l-boun...@securecoding.org] On
Behalf Of Wall, Kevin
Sent: Thursday, January 07, 2010 12:37 PM
To: 'ljknews'; Secure Coding
Subject: Re: [SC-L] 2010 bug hits millions of Germans | World news | The
Guardian
Larry Kilgallen wrote...
At 10:43 AM -0600 1/7/10, Stephen Craig
... and of course Multics solved the Y2K problem in 1965,
deferring the overflow for many additional decades.
___
Secure Coding mailing list (SC-L) SC-L@securecoding.org
List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l
List
It also solved the buffer overflow problem, and a number of others.
*sigh*
Matt
On Jan 7, 2010, at 8:15 PM, Peter G. Neumann wrote:
... and of course Multics solved the Y2K problem in 1965,
deferring the overflow for many additional decades.
___
At 10:43 AM -0600 1/7/10, Stephen Craig Evans wrote:
I am VERY curious to learn how these happened... Only using the last
digit of the year? Hard for me to believe. Maybe it's in a single API
and somebody tried to be too clever with some bit-shifting.
My wife says that in the lead-up to the
On Thu, 7 Jan 2010, Stephen Craig Evans wrote:
I am VERY curious to learn how these happened...
My name is Steve. I had a 2010 problem.
An internal CVE support program was hit by this issue. Fortunately,
there weren't any fatal results and it was only an annoyance. However: I
had an
Stephen Craig Evans wrote...
Looks like there's another one:
Symantec Y2K10 Date Stamp Bug Hits Endpoint Protection Manager
http://www.eweek.com/c/a/Security/Symantec-Y2K10-Date-Stamp-Bu
g-Hits-Endpoint-Protection-Manager-472518/? kc=EWKNLSTE01072010STR1
I am VERY curious to learn how these
Larry Kilgallen wrote...
At 10:43 AM -0600 1/7/10, Stephen Craig Evans wrote:
I am VERY curious to learn how these happened... Only using the last
digit of the year? Hard for me to believe. Maybe it's in a
single API
and somebody tried to be too clever with some bit-shifting.
My wife
At 2:37 PM -0600 1/7/10, Wall, Kevin wrote:
Larry Kilgallen wrote...
At 10:43 AM -0600 1/7/10, Stephen Craig Evans wrote:
I am VERY curious to learn how these happened... Only using the last
digit of the year? Hard for me to believe. Maybe it's in a
single API
and somebody tried to be
