RE: Windows Time Synchronization - Best Practices

["Poof" <poof () fansubber com>]

Well, while this is a reaching link…

Server 1 and Server 2 have different times and some vital program becomes
open to tampering when not synced.

(Computer that controls clock-ins says that Person A clocked in an hour
before they did. Clocks get corrected and the user gets an extra hour of
work they didn't do on their paychecks... A DoS if Person A times this
correctly.)

Sorry, I suck at examples. *gets ready to delete his own email when(if) it
arrives*

~

________________________________________
From: full-disclosure-admin () lists netsys com
[mailto:full-disclosure-admin () lists netsys com] On Behalf Of Richard Stevens
Sent: Tuesday, October 19, 2004 10:22 AM
To: Bernardo Santos Wernesback; full-disclosure () lists netsys com
Subject: RE: [Full-disclosure] Windows Time Synchronization - Best Practices

Why FD? What is the direct security implications of this?
 
I'm sure someone can construct a rather tenuous link, but really....

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html