Re: [ath5k-devel] connection to hidden WPA2-networks fails

2009-01-06 Thread Manuel Fill
On Tue, 6 Jan 2009 10:07:28 -0500 "Bob Copeland" wrote: > On Tue, Jan 6, 2009 at 6:29 AM, Fabio Rossi wrote: > > The patch for an empty hidden SSID is already in wireless-testing > > (commit bae888b3ea89097dcb8b28573d8bd6fa1147bc31) but it's slightly > > different from the one I had proposed in

Re: [ath5k-devel] connection to hidden WPA2-networks fails

2009-01-06 Thread Bob Copeland
On Tue, Jan 6, 2009 at 6:29 AM, Fabio Rossi wrote: > The patch for an empty hidden SSID is already in wireless-testing (commit > bae888b3ea89097dcb8b28573d8bd6fa1147bc31) but it's slightly different from the > one I had proposed in the thread recalled by Bob. So it is, thanks Fabio. It looks lik

Re: [ath5k-devel] connection to hidden WPA2-networks fails

2009-01-06 Thread Fabio Rossi
On Monday 05 January 2009, Bob Copeland wrote: > On Sun, Jan 4, 2009 at 9:18 PM, Geoffrey McRae wrote: > > Isn't that patch slightly wrong anyway? > > > > If the length of the ssid is 0 why check its first byte? Without looking > > at the surrounding code, if that buffer is not allocated and we c

Re: [ath5k-devel] connection to hidden WPA2-networks fails

2009-01-05 Thread Bob Copeland
On Sun, Jan 4, 2009 at 9:18 PM, Geoffrey McRae wrote: > Isn't that patch slightly wrong anyway? > > If the length of the ssid is 0 why check its first byte? Without looking > at the surrounding code, if that buffer is not allocated and we check > the bytes value, it could cause a seg fault. As it

Re: [ath5k-devel] connection to hidden WPA2-networks fails

2009-01-04 Thread Geoffrey McRae
Isn't that patch slightly wrong anyway? If the length of the ssid is 0 why check its first byte? Without looking at the surrounding code, if that buffer is not allocated and we check the bytes value, it could cause a seg fault. I would think that the better way to write this would be: if ((ssid_

Re: [ath5k-devel] connection to hidden WPA2-networks fails

2009-01-04 Thread Bob Copeland
On Fri, Jan 02, 2009 at 07:56:22AM +0100, manuel.f...@chello.at wrote: > it seems as if there is a problem with the hidden network. I can't > uncloak the SSID because it isn't my network. Could you please tell me > if I did something wrong? This sounds similar to the problem from this thread:

[ath5k-devel] connection to hidden WPA2-networks fails

2009-01-04 Thread manuel.fill
hi, as the topic already tells it, I can't connect to a known wpa2 network anymore. I used to connect to it via wpa_supplicant in the past with 2.6.27.1, which worked fine, but since I did the upgrade to 2.6.28 it doesn't work anymore. My entry in the wpa_supplicant.conf looks like this: netwo