On Thu, 2008-03-20 at 00:04 +0200, Tomas Winkler wrote: > On Wed, Mar 19, 2008 at 10:15 PM, Johannes Berg > <johannes@xxxxxxxxxxxxxxxx> wrote: > > > > > 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). > > > > That agrees with what I did in mac80211, but not with Intel's hardware. > > You wish, you didn't have clue yourself :) I know :P I actually just cleaned up the original code (and added the distinction for TX-only keys.) Actually, it makes things quite complicated for the driver because it has to keep track of whether pairwise keys are enabled even if they are for an encryption algorithm that it doesn't handle. I suppose making mac80211 track that would be nicer. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
