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 Focus-Microsoft
[Top] [All Lists]

RE: Windows wireless flaw...

Subject: RE: Windows wireless flaw...
Date: Thu, 19 Jan 2006 07:01:19 -0600
HI all! :)

I don't understand how this is a Microsoft flaw.  Isn't this how ad-hoc
WLAN's work?

If you've got two machines on a table, both with the same SSID, but neither
one advertising - they wouldn't see each other and be unable to make a
connection.

Would this not be (more accurately stated as) a flaw in the way ad-hoc
networks are implemented?

- Stan :)

-----Original Message-----
From: Aaron Phillips [mailto:aaronwphillips@gmail.com] 
Sent: Tuesday, January 17, 2006 8:40 AM
To: focus-ms@securityfocus.com
Subject: Re: Windows wireless flaw...

Your assumptions are correct, sir, at least according to my (limited) tests.

Although it was covered in the blog post I think maybe I can paraphrase a
bit clearer. 

It's not so much which network you connect to initially, when that network
is no longer available Windows will try to set up an ad-hoc network with the
previous WLAN SSID on the 169.254.X.X subnet.

On Monday 16 January 2006 15:06, Michael.Wade@ferguson.com wrote:
I'm under the impression that this can be a problem even if the 
networks connected to previously were infrastructure types?

-----Original Message-----
From: jeff@shawgo.com [mailto:jeff@shawgo.com]
Sent: Monday, January 16, 2006 10:38 AM
To: focus-ms@securityfocus.com
Subject: Re: Windows wireless flaw...

I've seen this behavior for months.  It's real.

The steps listed in the article (firewall, "Infrastructure Only", 
etc.) are sufficient to nullify this flaw.

~Jeff




Has anyone tested this out? If so, what are you thinking about doing 
to prevent it?

http://blogs.washingtonpost.com/securityfix/2006/01/windows_feature.ht
ml

I'm trying to see if I can get my test machine to do it--incidentally 
I have noticed two ad-hoc networks these last two days. (One has a (1) 
appended to it--not sure what is adding the one).


Kind Regards
Murad Talukdar






------------------------------------------------------------------------
---
------------------------------------------------------------------------
---



------------------------------------------------------------------------
---
------------------------------------------------------------------------
---



---------------------------------------------------------------------------

---------------------------------------------------------------------------

-- 
//Begin sig

Aaron Phillips
Technician, SYSTECH Computers
989-743-4296

I sign all of my messages with a PGP Public Key using the Open Source
version 
of PGP, GNU Privacy Guard. More information is available at the website 
http://www.gnupg.org/

My public key is available for import on hkp://subkeys.pgp.net and also 
http://www.systech-computers.com/keys

//End sig

---------------------------------------------------------------------------
---------------------------------------------------------------------------

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