Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Pen-Test
[Top] [All Lists]

Re: Identifying Windows O/S & SP

Subject: Re: Identifying Windows O/S & SP
Date: Fri, 26 Aug 2005 15:48:30 +0100
On 8/24/05, L3wD <l3wd@earthlink.net> wrote:
    I am looking for a method of correctly identifying Windows O/S Versions 
and Service Packs remotely. Here are my restrictions:
- Performed Remotely (not in same broadcast domain)
- No Admin Rights on Remote Box
- No Username/Password on Remote Box
- VERY Few Packets Generated (excluding TCP 3-way handshake)
- Ability to **AVOID** IDS Detection

You should put this list to the NMAP summer of code team, they're
currently looking at reworking the whole TCP fingerprinting / OS
identification module.

I'm guessing much of what you want is going to be restricted by the
'few packets generated' condition - especially if it stops you from
establishing a connection to a remote TCP port for long enough to get
a banner message.
I suppose you'd need to plug in a sniffer and do some calibrating at
home first.  Eg - get your NT4 server, and sniff traffic from it, then
apply SP1, repeat, apply SP2, etc... then look to see what's changed.

-- 
AdamT
"Maidenhead is *not* in Kent"

<Prev in Thread] Current Thread [Next in Thread>