full-disclosure - Windows Time Synchronization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <117C14E37DABD242A0EE9ABB759F29D50DE57C@webmail.tccnet.co.uk>
From: richard at tccnet.co.uk (Richard Stevens)
Subject: 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/18035d83/attachment.html