[<prev] [next>] [day] [month] [year] [list]
Message-ID: <9E97F0997FB84D42B221B9FB203EFA27171EF2@dc1ms2.msad.brookshires.net>
From: toddtowles at brookshires.com (Todd Towles)
Subject: Windows Time Synchronization - Best Practices
As everyone knows, there is very little that is OT on FD...so if you
don't have anything nice to say....shhh! lol
________________________________
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of Richard
Stevens
Sent: Tuesday, October 19, 2004 12:22 PM
To: Bernardo Santos Wernesback; full-disclosure@...ts.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....
-----Original Message-----
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com]On Behalf Of Bernardo
Santos Wernesback
Sent: 19 October 2004 16:05
To: full-disclosure@...ts.netsys.com
Subject: [Full-Disclosure] Windows Time Synchronization
- Best Practices
Hello everyone,
I was wondering if anyone has or could point me to some
sort of paper describing best-practices related to time synchronization
and the configuration of daylight savings.
Basically my problem is deciding if I should or
shouldn't use Windows' option to autoconfigure daylight savings but I'd
like to see recommendations from known companies.
I am also open to suggestions from the Full-disclosure
community but my recommendations have to be justified to my boss ;)
Thanks for any pointers!
See ya,
Bernardo Santos Wernesback
bernardo@....com.br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20041019/b2818635/attachment.html
Powered by blists - more mailing lists