bugtraq - RE: Microsoft updates documentation on 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: <20040824211829.ZKWM8513.amsfep20-int.chello.nl@HPT580>
Date: Tue, 24 Aug 2004 23:17:51 +0200
From: "Nicolas villatte" <Nicolas.Villatte@...alvas.be>
To: "'3APA3A'" <3APA3A@...URITY.NNOV.RU>, <bugtraq@...urityfocus.com>,
   <NTBUGTRAQ@...TSERV.NTBUGTRAQ.COM>, <full-disclosure@...ts.netsys.com>
Subject: RE: Microsoft updates documentation on Windows time synchronization

Cisco routers support only MD5 authentication for NTP
(http://www.oreilly.com/catalog/hardcisco/chapter/ch10.html).

I have found documentation to update ntp clients on unix systems using this
MD5 authentication but not the equivalent for Windows 2000/2003 ntp client.
Does someone knows if it is feasible and how?

Thanks,

Nicolas.

> Microsoft  published  Q884776  "Configuring  the  Windows Time service
>  against a large time offset"
>
>  http://support.microsoft.com/default.aspx?scid=kb;en-us;884776
>
>  In  addition to clear description on new registry keys in Windows 2000
>  SP4  and  Windows  2003 Microsoft added recommendation to use hardware
>  time  source.  Design flaw is currently fixed by documentation. I hope
>  finally   MS   will   implement   signing   at   least  for  it's  own
>  time.windows.com.

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