From: Dan Williams <dcbw@redhat.com>
To: Masakazu Mokuno <mokuno@sm.sony.co.jp>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, cbe-oss-dev@ozlabs.org,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Stefan Assmann <sassmann@suse.de>
Subject: Re: [PATCH] PS3: gelic: ignore scan info from zero SSID beacons
Date: Wed, 12 Mar 2008 09:42:31 -0400 [thread overview]
Message-ID: <1205329351.32049.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20080312182438.0B1F.40F06B3A@sm.sony.co.jp>
On Wed, 2008-03-12 at 19:26 +0900, Masakazu Mokuno wrote:
> On Wed, 12 Mar 2008 09:25:10 +0100
> Johannes Berg <johannes@sipsolutions.net> wrote:
>
> >
> > > > Does this problem apply to probe responses as well? (Do probe
> > > > responses from hidden SSID APs still exclude the SSID? I would
> > > > guess not.)
> > >
> > > There has been a problem in parsing IEs, so if the received probe
> > > responses include zero length IEs, they also suffer this bug.
> > >
> > > > As long as you can still associate w/ hidden SSID APs, I don't see
> > > > a big problem. Even if you can't, no information for those APs is
> > > > probably better than bad information, no?
> > >
> > > I was anxious that the userland apps or the users may get confused. Any
> > > other thing harmful is not found.
> > > OK, I withdraw this patch.
> >
> > I think John actually meant that it would be better to have the patch
> > in. How does a "bad" scan result look like?
>
> Usually the zero length IE, the SSID element, is the first one of IE
> list, all information in the successor elements is lost. What we can see
> is bssid.
>
> The current firmware gives the following result. The Corega (00:0A:79)
> AP was the one which sent zero length SSID if it was in hidden SSID mode.
>
> > iwlist wlan0 scanning
> > wlan0 Scan completed :
> > Cell 01 - Address: 00:06:25:C6:B9:A7
> > ESSID:"planexuser"
> > Channel=1
> > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
> > 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
> > 48 Mb/s; 54 Mb/s
> > Encryption key:on
> > Mode:Master
> > Signal level=100/100
> > IE: IEEE 802.11i/WPA2 Version 1
> > Group Cipher : CCMP
> > Pairwise Ciphers (1) : CCMP
> > Authentication Suites (1) : PSK
> > Cell 02 - Address: 00:0A:79:A5:D2:E2
> > ESSID:""
> > Channel:0
> > Encryption key:on
> > Mode:Master
> > Signal level=100/100
Ewww. You're 100% correct; we certainly shouldn't be sending a scan
result like this to userspace. Therefore:
Acked-by: Dan Williams <dcbw@redhat.com>
>
> With fixed firmware:
>
> > wlan0 Scan completed :
> > Cell 01 - Address: 00:06:25:C6:B9:A7
> > ESSID:"planexuser"
> > Channel=1
> > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
> > 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
> > 48 Mb/s; 54 Mb/s
> > Encryption key:on
> > Mode:Master
> > Signal level=100/100
> > IE: IEEE 802.11i/WPA2 Version 1
> > Group Cipher : CCMP
> > Pairwise Ciphers (1) : CCMP
> > Authentication Suites (1) : PSK
> > Cell 02 - Address: 00:0A:79:A5:D2:E2
> > ESSID:""
> > Channel:1
> > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
> > 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
> > 48 Mb/s; 54 Mb/s
> > Encryption key:on
> > Mode:Master
> > Signal level=100/100
> > IE: IEEE 802.11i/WPA2 Version 1
> > Group Cipher : CCMP
> > Pairwise Ciphers (1) : CCMP
> > Authentication Suites (1) : PSK
> >
>
>
next prev parent reply other threads:[~2008-03-12 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 4:15 [PATCH] PS3: gelic: ignore scan info from zero SSID beacons Masakazu Mokuno
2008-03-11 16:18 ` Johannes Berg
2008-03-11 16:50 ` Dan Williams
2008-03-11 17:10 ` John W. Linville
2008-03-12 2:18 ` Masakazu Mokuno
2008-03-12 8:25 ` Johannes Berg
2008-03-12 10:26 ` Masakazu Mokuno
2008-03-12 13:42 ` Dan Williams [this message]
2008-03-12 14:31 ` Johannes Berg
2008-03-12 14:43 ` Johannes Berg
2008-03-13 7:01 ` Masakazu Mokuno
2008-03-12 2:24 ` Masakazu Mokuno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1205329351.32049.8.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mokuno@sm.sony.co.jp \
--cc=sassmann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).