linux-kernel - Re: Required sequence to set wireless parameters?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1237490871.5100.113.camel@johannes.local>
Date:	Thu, 19 Mar 2009 20:27:51 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Frans Pop <elendil@...net.nl>
Cc:	"John W. Linville" <linville@...driver.com>,
	jeff.chua.linux@...il.com, mingo@...e.hu,
	torvalds@...ux-foundation.org, rjw@...k.pl,
	linux-kernel@...r.kernel.org, bunk@...nel.org,
	akpm@...ux-foundation.org, kernel-testers@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: Required sequence to set wireless parameters?

On Thu, 2009-03-19 at 20:24 +0100, Frans Pop wrote:

> > > Reason I ask is that for example when writing wireless support for
> > > e.g. a distro installation system, it seems most logical to *first*
> > > ask the user what network (ESSID) he wants to connect to. Next to
> > > check if we can connect to that network without additional
> > > authentication and only then, if needed, ask for keys etc.
> > > If it's not possible to set that info in that logical order that
> > > seems rather restrictive to me and would probably mean that you'd
> > > have to reset AP, ESSID and possibly other settings before each
> > > incremental attempt.
> >
> > That's a pretty wrong argument, nothing says your software cannot
> > collect all the information and then give it to the kernel at once
> > later, I think... In fact, this is required anyway when you use RSN or
> > WPA (wpa_supplicant needs all information at once), for example.
> 
> Well, the thing is that we'll already have tried just setting essid to 
> check if it's an open network. However, I can see the point of needing to 
> set the essid _again_ after asking the key info and setting that.

Ah.

> I can also see how you might have to unset some settings in some cases, 
> for example if the NIC has already associated with the wrong network 
> (e.g. because there's a totally open network in range).

No, there should be no need for that really, an
	iwconfig wlan0 ap any
should always make it associate with the current settings.

Now, this thread is about why it doesn't for Jeff :)

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)