Ars TechnicaWindows feature that resets system clocks based on random data is wreaking havoc
Windows Secure Time Seeding resets clocks months or years off the correct time.
Chris Glass@arstechnica if I'm reading this right, it's because the SSL Handshake response uses random data and Windows assumed it was a Unix timestamp?
Will@TheChrisGlass @arstechnica my read is that in the spec the handshake/communication requires a number that should always be different in each message. and it traditionally has been the unix time or partially composed from unix time. but there are implantations that use a random number instead to increase security.