All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] [PATCH 1/5] mac80211: allows driver to request a Phase 2 key
Date: Wed, 19 Mar 2008 22:10:04 +0200	[thread overview]
Message-ID: <20080319201004.GC5308@jm.kir.nu> (raw)
In-Reply-To: <1ba2fa240803191141y7feae800g607432f2e9628e37@mail.gmail.com>

On Wed, Mar 19, 2008 at 08:41:22PM +0200, Tomas Winkler wrote:

> So how do you call WEP key that is used for both unicast and broadcast
> i.e the old WEP key.

The IEEE 802.11 name for this would be "default key". IEEE 802.1X (or
well, RFC 3580 is the authoritative specification for this) calls it
"broadcast (default key)". Please note that this is not really a key
that is always used both for unicast and broadcast. If there is a
key-mapping key (unicast/individual) for the matching
transmitter/receiver addresses, that key will be used instead. The "old
WEP key" way of using only statically configured default keys just does
not set the key-mapping key and because of that, the default key ends up
being used for all frames (or well, one of the possible four default
keys).

> What mac80211 currently does it's attach it to broadcast address. If
> there is a group key re keying you don't know whether also unicast key
> have to be overridden or not since you don't know if this is a
> 'static/global; key or  dynamic group key

I haven't looked at what the current implementation does, but as far as
WEXT and SIOCSIWENCODEEXT is concerned, IW_ENCODE_EXT_GROUP_KEY flag
should be used to select which key is being configured. There is no
difference between "static/global" and "dynamic group" keys. The only
difference is between default and key-mapping (individual) keys.

Sure, the terminology here can be quite confusing, but as far as I can
tell, that IW_ENCODE_EXT_GROUP_KEY flag is all that is needed to
distinguish which key is being configured and configuring a single key
should not automatically change another one (even if the key index is
same which could, at least in theory, happen with key index 0 that can
be used both with default and key-mapping keys).

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2008-03-19 20:10 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13  0:05 [PATCH 0/5] iwlwifi driver updates Reinette Chatre
2008-03-13  0:05 ` [PATCH 1/5] mac80211: allows driver to request a Phase 2 key Reinette Chatre
2008-03-13  0:05   ` [PATCH 2/5] mac80211: allows driver to request a Phase 1 RX key Reinette Chatre
2008-03-13  0:06     ` [PATCH 3/5] iwlwifi-2.6: Cleans up set_key flow Reinette Chatre
2008-03-13  0:06       ` [PATCH 4/5] iwlwifi-2.6: enables HW TKIP security Reinette Chatre
2008-03-13  0:06         ` [PATCH 5/5] iwlwifi-2.6: RX status translation to old scheme Reinette Chatre
2008-03-15 19:11     ` [PATCH 2/5] mac80211: allows driver to request a Phase 1 RX key Johannes Berg
2008-03-17  0:04       ` [ipw3945-devel] " Tomas Winkler
2008-03-17 11:39         ` Johannes Berg
2008-03-17 13:03           ` Tomas Winkler
2008-03-17 13:13             ` Johannes Berg
2008-03-17 14:45               ` Tomas Winkler
2008-03-17 15:04                 ` Johannes Berg
2008-03-17 19:54                   ` Tomas Winkler
2008-03-17 20:02                     ` Johannes Berg
2008-03-17 20:20                       ` Tomas Winkler
2008-03-15 14:38   ` [PATCH 1/5] mac80211: allows driver to request a Phase 2 key Johannes Berg
2008-03-17  0:21     ` [ipw3945-devel] " Tomas Winkler
2008-03-17  9:58       ` Johannes Berg
2008-03-17 10:20         ` Tomas Winkler
2008-03-17 10:57           ` Johannes Berg
2008-03-17 12:40             ` Tomas Winkler
2008-03-17 12:51               ` Johannes Berg
2008-03-17 13:36                 ` Tomas Winkler
2008-03-17 13:49                   ` Johannes Berg
2008-03-17 19:12                     ` Tomas Winkler
2008-03-17 19:19                       ` Johannes Berg
2008-03-17 19:39                         ` Tomas Winkler
2008-03-17 20:04                           ` Johannes Berg
2008-03-17 20:27                             ` Tomas Winkler
2008-03-17 20:59                               ` Johannes Berg
2008-03-18  8:04                               ` Jouni Malinen
2008-03-18  9:18                                 ` Johannes Berg
2008-03-18 10:23                                   ` Jouni Malinen
     [not found]                                     ` <8704f27d0803190942h19b5a9ebjd3b27537c30ef719@mail.gmail.com>
2008-03-19 17:39                                       ` Jouni Malinen
2008-03-19 18:41                                         ` Tomas Winkler
2008-03-19 20:10                                           ` Jouni Malinen [this message]
2008-03-19 20:15                                             ` Johannes Berg
2008-03-19 22:04                                               ` Tomas Winkler
2008-03-19 22:11                                                 ` Johannes Berg
2008-03-19 20:56                                             ` Tomas Winkler
2008-03-20  7:09                                             ` Emmanuel Grumbach
2008-03-20  7:36                                               ` Jouni Malinen
2008-03-17 21:06                     ` Dan Williams
2008-03-17 23:26                       ` Tomas Winkler
2008-03-17 21:23           ` Dan Williams
2008-03-17 23:35             ` Tomas Winkler

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=20080319201004.GC5308@jm.kir.nu \
    --to=j@w1.fi \
    --cc=egrumbach@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.