mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Weird wireless/wpa_supplicant screw-up.
Date: Tue, 16 Mar 2010 20:22:30 -0700	[thread overview]
Message-ID: <1268796150.7068.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <12262.1268795213@localhost>

On Tue, 2010-03-16 at 23:06 -0400, Valdis.Kletnieks@vt.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


  reply	other threads:[~2010-03-17  3:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 22:22 Valdis.Kletnieks
2010-03-12 11:14 ` Johannes Berg
2010-03-12 11:16   ` Johannes Berg
2010-03-12 21:49   ` Valdis.Kletnieks
2010-03-12 22:19     ` Pavel Roskin
2010-03-12 22:22       ` Valdis.Kletnieks
2010-03-13  3:09     ` Johannes Berg
2010-03-17  3:06       ` Valdis.Kletnieks
2010-03-17  3:22         ` Johannes Berg [this message]
2010-03-17  8:21           ` Valdis.Kletnieks
2010-03-17  9:03             ` Holger Schurig
2010-03-17 20:29               ` Valdis.Kletnieks

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=1268796150.7068.6.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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

Powered by JetHome