nl80211: Ignore seq number for key deletion
Turns out we are sometime providing a seq when deleting the key. Since that makes no sense on key deletion let's stop forwarding that to the driver at least. Signed-off-by: Alexander Wetzel <alexander@wetzel-home.de>
This commit is contained in:
parent
e9e69221c1
commit
adf550ee4b
1 changed files with 6 additions and 5 deletions
|
@ -3118,12 +3118,13 @@ static int wpa_driver_nl80211_set_key(struct i802_bss *bss,
|
||||||
nla_put_u32(key_msg, NL80211_KEY_CIPHER, suite))
|
nla_put_u32(key_msg, NL80211_KEY_CIPHER, suite))
|
||||||
goto fail;
|
goto fail;
|
||||||
wpa_hexdump_key(MSG_DEBUG, "nl80211: KEY_DATA", key, key_len);
|
wpa_hexdump_key(MSG_DEBUG, "nl80211: KEY_DATA", key, key_len);
|
||||||
}
|
|
||||||
|
|
||||||
if (seq && seq_len) {
|
if (seq && seq_len) {
|
||||||
if (nla_put(key_msg, NL80211_KEY_SEQ, seq_len, seq))
|
if (nla_put(key_msg, NL80211_KEY_SEQ, seq_len, seq))
|
||||||
goto fail;
|
goto fail;
|
||||||
wpa_hexdump(MSG_DEBUG, "nl80211: KEY_SEQ", seq, seq_len);
|
wpa_hexdump(MSG_DEBUG, "nl80211: KEY_SEQ",
|
||||||
|
seq, seq_len);
|
||||||
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
if (addr && !is_broadcast_ether_addr(addr)) {
|
if (addr && !is_broadcast_ether_addr(addr)) {
|
||||||
|
|
Loading…
Reference in a new issue