On Fri, 2007-08-17 at 10:16 -0400, Volker Braun wrote: > NetworkManager can do that for you, no need to duplicate that in the > driver where you can't give any useful feedback to the user. Maybe you > want to test whether your AP _really_ discards unencrypted data? Can't really do that since it'll ack the packet anyway :) > It should be broadcast, you are right. Don't think it matters much, was just curious. > The key index is saved later on in key->keyidx. So I wanted to be on the > safe side and make sure that a legal value is stored there. Right. I was totally confused about some things and just reread the standard again :) > First of all, we violate the standard by looking at the keyindex in case > of a pairwise key. I don't think we do look at it, do we? In any case, if it was there I removed it with the RFC key selection patch. > Now granted, Cisco also violates it, but in a way > that is never visible to standards-compliant STAs. We must set the > keyindex to zero on outgoing pairwise key-encrypted data, but that is > kind of irrelevant since the AP is forced to ignore that key index on > receive. But then I don't understand why we try to set a non-zero key index for the key. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
