From: Jouni Malinen <jkmaline@cc.hut.fi>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: Netdev <netdev@oss.sgi.com>, prism54-devel@prism54.org
Subject: Re: Prism54 wpa update
Date: Tue, 29 Jun 2004 18:49:30 -0700 [thread overview]
Message-ID: <20040630014930.GB7153@jm.kir.nu> (raw)
In-Reply-To: <20040629192101.GB14482@ruslug.rutgers.edu>
On Tue, Jun 29, 2004 at 03:21:01PM -0400, Luis R. Rodriguez wrote:
> I'll keep my latest wpa work/patch at the following URL:
>
> http://prism54.org/~mcgrof/prism54-wpa.diff
Hmm.. I do not understand the change you did for priv->wpa processing.
There seems to be some kind of misunderstanding on what DOT11_AUTHENABLE
and DOT11_OID_MLMEAUTOLEVEL is set to in various mode. I do not fully
understand what you mean with TKIP vs 802.1x. TKIP is an encryption
algorithm like WEP. IEEE 802.1X is authentication protocol which can be
used with IEEE 802.1X EAPOL-Key frames to distribute WEP keys _or_ with
WPA to generate keying material for WPA 4-Way Handshake that will
generate the data encryption keys.
DOT11_AUTHENABLE should be set to DOT11_AUTH_OS for WPA modes (i.e., not
_SK or _BOTH like you had in some cases). DOT11_AUTH_SK can only be used
with static WEP configuration (i.e., not with WPA or with IEEE 802.1X
when using dynamic WEP key generation). DOT11_AUTH_BOTH is likewise only
reasonable for static WEP configuration since it includes _SK as an
option. DOT11OID_MLMEAUTOLEVEL seems to be required to be
DOT11_MLME_EXTENDED for all cases where WPA IE is used.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2004-06-30 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 19:21 Prism54 wpa update Luis R. Rodriguez
2004-06-29 20:22 ` Jeff Garzik
2004-06-30 14:01 ` Luis R. Rodriguez
2004-06-30 1:49 ` Jouni Malinen [this message]
2004-06-30 15:13 ` [Prism54-devel] " Luis R. Rodriguez
2004-06-30 15:45 ` Jouni Malinen
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=20040630014930.GB7153@jm.kir.nu \
--to=jkmaline@cc.hut.fi \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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).