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-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0410190902110.20146@catbert.rellim.com>
From: gem at rellim.com (Gary E. Miller)
Subject: Windows Time Synchronization - Best Practices

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yo Bernardo!

On Tue, 19 Oct 2004, Bernardo Santos Wernesback wrote:

> 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.

Not sure where to find the paper you are looking for.  In my experience
NTP will work a lot better for you than Windows Time server.

Here is some info on NTP:
	http://www.ntp.org/ntpfaq/NTP-s-def.htm

With NTP you can get your time from a large diverse set of accurate
time server.  The protocol is robust and you are not dependent on the
single point of failure called: time.microsoft.com.

If your time needs are critical you can also use NTP to get time from
GPS or other very accurate sources and server it to your net.

Tardis is one of the better NTP clients for windows:
	http://www.kaska.demon.co.uk/

RGDS
GARY
- ---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Blvd, Suite E-3, Bend, OR 97701
	gem@...lim.com  Tel:+1(541)382-8588 Fax: +1(541)382-8676

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFBdTwl8KZibdeR3qURAjftAJwMK9kU7x0fTXg67nrPVgYCrArHqgCgzBjC
HjcWOCA8TSO5T6Fr+DUYLZM=
=X2tT
-----END PGP SIGNATURE-----