Vulnerability Development mailing list archives

Re: Windows XP RC2


From: "Gregory McCann" <cambria () owt com>
Date: Mon, 20 Aug 2001 20:40:21 -0700

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

Greg

On 8/20/2001 at 12:21 PM bugtraq wrote:

Hi Listers,

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
out
there, it would throw a big monkey wrench into the statistics (if any)
that
M$ is gathering.

Take Care,
Duane.



At 06:36 AM 8/20/2001, you wrote:
Well I am not sure if you would consider this a bug, incident, monitoring
or
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
it,
but what is disturbing is take a guess as to what the "default" Time
Server
that gets used???

time.windows.com  !!!


Well for every install M$ can monitor/track who is running XP that has a
Net
connection.
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
be
communicated to once they grab the IP that queries their time server?!

Thanks for listening

Dino




Current thread: