Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Gregory McCann (cambriaowt.com)
Date: Mon Aug 20 2001 - 22:40:21 CDT
Apologies if I am missing something here, but the Microsoft time server is time.windows.com (as stated in the original message far below), not time.microsoft.com.
Anyone can easily connect to it. I use the "Dimension 4" time client on my Windows ME PC and simply added an entry for the time.windows.com SNTP server and it worked fine. It was about 2 seconds ahead of the time server I currently use.
In *nix, it's "ntpdate time.windows.com".
On 8/20/2001 at 12:21 PM bugtraq wrote:
>I am new to this list and if my reply is out of line, please forgive me.
>How hard would it be to write a pseudo client for the *nix os's that would
>query time.microsoft.com and then use or not use the information as the
>programmer would deem appropriate? If there were enough pseudo clients
>there, it would throw a big monkey wrench into the statistics (if any)
>M$ is gathering.
>At 06:36 AM 8/20/2001, you wrote:
>>Well I am not sure if you would consider this a bug, incident, monitoring
>>a feature, but in Windows XP RC2 that we loaded this weekend
>>I noticed that M$ has Network Time Client built to keep correct time.
>>This is good so that we do not have to grab a 3rd party app and install
>>but what is disturbing is take a guess as to what the "default" Time
>>that gets used???
>>Well for every install M$ can monitor/track who is running XP that has a
>>Yes you can simply pick another like my favorite
>>"time-a.timefreq.bldrdoc.gov" and all is well, but that average user wont
>>know this and may not even care, but they should ;)
>>If your real paranoid one can think well if the NTP is using
>>time.windows.com what is stopping M$ from having some hidden app that can
>>communicated to once they grab the IP that queries their time server?!
>>Thanks for listening