linux-kernel - Re: Weird wireless/wpa

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: <1268796150.7068.6.camel@jlt3.sipsolutions.net>
Date:	Tue, 16 Mar 2010 20:22:30 -0700
From:	Johannes Berg <johannes@...solutions.net>
To:	Valdis.Kletnieks@...edu
Cc:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: Weird wireless/wpa_supplicant screw-up.

On Tue, 2010-03-16 at 23:06 -0400, Valdis.Kletnieks@...edu wrote:
> On Fri, 12 Mar 2010 19:09:09 PST, Johannes Berg said:
> > No ... look at _all_ that it produces.
> > 
> > [   98.592575] In giwencode idx=0 keys=ffff88001b304000 cipher=0
> > [   98.592580] And we're going home...
> > *****
> > [   98.592633] In giwencode idx=1 keys=ffff88001b304000 cipher=fac04
> > *****
> > [   98.592749] In giwencode idx=2 keys=ffff88001b304000 cipher=0
> > [   98.592751] And we're going home...
> > [   98.592803] In giwencode idx=3 keys=ffff88001b304000 cipher=0
> > [   98.592805] And we're going home...
> > [   98.592856] In giwencode idx=0 keys=ffff88001b304000 cipher=0
> > [   98.592859] And we're going home...
> > 
> > See? It reports one key which is the RX-only group key which is
> > absolutely correct.
> 
> It matches what 'iwlist keys' reports, but I remain unconvinced of
> its "correctness".  

That's your problem then, not mine. It's correct in how wext operates.
If you want to know why, you'll have to understand the distinction
between PTK and GTK and how wext operates with them.

> If a TX key has been set anyplace, what allows me
> to verify that it was in fact set?

Nothing. Blame it on wext and on the fact that nobody cares.

> > > So the root cause has something to do with params[idx].cipher being unset.
> > 
> > Not at all.
> 
> I was referring to the root cause of why 'iwlist keys' wasn't reporting
> anything for the other 3 key slots.

Right ... all of that is completely correct. See above about PTK and
GTK ... You seem to not be interested in telling me what your actual
problem is, if there is one. If your actual problem is just that iwlist
reports what you think is wrong information (which is just incomplete,
it doesn't show the PTK) then that's nothing I actually care about
fixing.

> I'll point out that until fairly recently 'iwconfig' *did* report a
> key for WPA2, so this looks like a regression on somebody's part.

I'm sure it did not.

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/