netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: netdev@vger.kernel.org
Subject: Re: Problem authenticating using WPA with bcm43xx-softmac
Date: Wed, 07 Jun 2006 17:51:09 +0200	[thread overview]
Message-ID: <1149695470.3925.7.camel@johannes> (raw)
In-Reply-To: <4486F513.5050906@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

On Wed, 2006-06-07 at 10:47 -0500, Larry Finger wrote:

> I have a little more information on what is happening. 

Great.

> In IEEE Std 802.11i-2004, which defines the 
> WPA protocol, Figure 11a shows the sequence of exchanges needed to associate. Both bcm43xx-softmac 
> and ndiswrapper go through the "Open System Authentication" process. 

Right, you always have to do that.

> Where they seem to diverge is 
> in the STA's "Association Request (Security Parameters)" step. With ndiswrapper, the AP responds 
> with a WPA EAPOL-Key message; whereas with softmac, the AP sends back the "invalid pairwise cipher 
> message" and rejects the association.

Interesting. That's strange.

> Can anyone point to a reference that states what the content of the Association Request should be to 
> get the AP to respond with the EAPOL-Key message? Unfortunately, I have no possibility of 
> implementing a sniffer to see what a "correct" message contains.

Well, it should be shown in the 802.11i spec too.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]

  reply	other threads:[~2006-06-07 15:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 19:24 Problem authenticating using WPA with bcm43xx-softmac Larry Finger
2006-06-07 12:10 ` Johannes Berg
2006-06-07 15:47   ` Larry Finger
2006-06-07 15:51     ` Johannes Berg [this message]
2006-06-07 15:57       ` Johannes Berg
2006-06-07 17:29         ` Dan Williams
2006-06-07 18:12           ` Larry Finger
2006-06-07 19:36             ` Dan Williams
2006-06-07 19:46               ` Larry Finger
2006-06-09 11:44             ` Johannes Berg
2006-06-09 15:31               ` Larry Finger
2006-06-09 15:34                 ` Johannes Berg
2006-06-09 16:24                   ` Larry Finger
2006-06-12  1:11                   ` Larry Finger
2006-06-13  8:40                     ` Johannes Berg
2006-06-07 16:01       ` Sam Leffler
2006-06-07 16:06         ` Johannes Berg
2006-06-07 16:30           ` Larry Finger
2006-06-07 17:07           ` Larry Finger
2006-06-07 16:09         ` Larry Finger

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=1149695470.3925.7.camel@johannes \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).