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: <3587D6FDF44881459313970A8DE75A81015FF741@exchange.quadrasis.com>
From: David.Cushing at hitachisoftware.com (Cushing, David)
Subject: Windows Time Synchronization - Best Practices

> In my experience NTP will work a lot better for 
> you than Windows Time server.

Windows time service uses SNTP.

> The protocol is robust and you are not dependent on the
> single point of failure called: time.microsoft.com.

Never heard of time.microsoft.com being down or incorrect.  You can use 'net time' or regedit to change it.

http://www.microsoft.com/windows2000/docs/wintimeserv.doc