* [PATCH 5.3] rt2x00: clear up IV's on key removal
@ 2019-08-23 12:48 Stanislaw Gruszka
2019-08-27 8:30 ` Emil Karlson
2019-09-03 13:52 ` Kalle Valo
0 siblings, 2 replies; 3+ messages in thread
From: Stanislaw Gruszka @ 2019-08-23 12:48 UTC (permalink / raw)
To: linux-wireless
Cc: Felix Fietkau, Daniel Golle, Tomislav Požega,
Mathias Kresin, Emil Karlson, Fredrik Noring
After looking at code I realized that my previous fix
95844124385e ("rt2x00: clear IV's on start to fix AP mode regression")
was incomplete. We can still have wrong IV's after re-keyring.
To fix that, clear up IV's also on key removal.
Fixes: 710e6cc1595e ("rt2800: do not nullify initialization vector data")
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
---
drivers/net/wireless/ralink/rt2x00/rt2800lib.c | 19 ++++++++++++-------
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
index ecbe78b8027b..28e2de04834e 100644
--- a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
+++ b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
@@ -1654,13 +1654,18 @@ static void rt2800_config_wcid_attr_cipher(struct rt2x00_dev *rt2x00dev,
offset = MAC_IVEIV_ENTRY(key->hw_key_idx);
- rt2800_register_multiread(rt2x00dev, offset,
- &iveiv_entry, sizeof(iveiv_entry));
- if ((crypto->cipher == CIPHER_TKIP) ||
- (crypto->cipher == CIPHER_TKIP_NO_MIC) ||
- (crypto->cipher == CIPHER_AES))
- iveiv_entry.iv[3] |= 0x20;
- iveiv_entry.iv[3] |= key->keyidx << 6;
+ if (crypto->cmd == SET_KEY) {
+ rt2800_register_multiread(rt2x00dev, offset,
+ &iveiv_entry, sizeof(iveiv_entry));
+ if ((crypto->cipher == CIPHER_TKIP) ||
+ (crypto->cipher == CIPHER_TKIP_NO_MIC) ||
+ (crypto->cipher == CIPHER_AES))
+ iveiv_entry.iv[3] |= 0x20;
+ iveiv_entry.iv[3] |= key->keyidx << 6;
+ } else {
+ memset(&iveiv_entry, 0, sizeof(iveiv_entry));
+ }
+
rt2800_register_multiwrite(rt2x00dev, offset,
&iveiv_entry, sizeof(iveiv_entry));
}
--
1.9.3
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 5.3] rt2x00: clear up IV's on key removal
2019-08-23 12:48 [PATCH 5.3] rt2x00: clear up IV's on key removal Stanislaw Gruszka
@ 2019-08-27 8:30 ` Emil Karlson
2019-09-03 13:52 ` Kalle Valo
1 sibling, 0 replies; 3+ messages in thread
From: Emil Karlson @ 2019-08-27 8:30 UTC (permalink / raw)
To: Stanislaw Gruszka
Cc: linux-wireless, Felix Fietkau, Daniel Golle,
Tomislav Požega, Mathias Kresin, Fredrik Noring
On Fri, 23 Aug 2019 14:48:03 +0200
Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> After looking at code I realized that my previous fix
> 95844124385e ("rt2x00: clear IV's on start to fix AP mode regression")
> was incomplete. We can still have wrong IV's after re-keyring.
> To fix that, clear up IV's also on key removal.
>
> Fixes: 710e6cc1595e ("rt2800: do not nullify initialization vector
> data") Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
> drivers/net/wireless/ralink/rt2x00/rt2800lib.c | 19
> ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
> b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c index
> ecbe78b8027b..28e2de04834e 100644 ---
> a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c +++
> b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c @@ -1654,13 +1654,18
> @@ static void rt2800_config_wcid_attr_cipher(struct rt2x00_dev
> *rt2x00dev, offset = MAC_IVEIV_ENTRY(key->hw_key_idx);
>
> - rt2800_register_multiread(rt2x00dev, offset,
> - &iveiv_entry, sizeof(iveiv_entry));
> - if ((crypto->cipher == CIPHER_TKIP) ||
> - (crypto->cipher == CIPHER_TKIP_NO_MIC) ||
> - (crypto->cipher == CIPHER_AES))
> - iveiv_entry.iv[3] |= 0x20;
> - iveiv_entry.iv[3] |= key->keyidx << 6;
> + if (crypto->cmd == SET_KEY) {
> + rt2800_register_multiread(rt2x00dev, offset,
> + &iveiv_entry,
> sizeof(iveiv_entry));
> + if ((crypto->cipher == CIPHER_TKIP) ||
> + (crypto->cipher == CIPHER_TKIP_NO_MIC) ||
> + (crypto->cipher == CIPHER_AES))
> + iveiv_entry.iv[3] |= 0x20;
> + iveiv_entry.iv[3] |= key->keyidx << 6;
> + } else {
> + memset(&iveiv_entry, 0, sizeof(iveiv_entry));
> + }
> +
> rt2800_register_multiwrite(rt2x00dev, offset,
> &iveiv_entry,
> sizeof(iveiv_entry)); }
Seems to work when used with the previous patch on top of 5.3-rc6
tested-by: Emil Karlson <jekarl@iki.fi>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 5.3] rt2x00: clear up IV's on key removal
2019-08-23 12:48 [PATCH 5.3] rt2x00: clear up IV's on key removal Stanislaw Gruszka
2019-08-27 8:30 ` Emil Karlson
@ 2019-09-03 13:52 ` Kalle Valo
1 sibling, 0 replies; 3+ messages in thread
From: Kalle Valo @ 2019-09-03 13:52 UTC (permalink / raw)
To: Stanislaw Gruszka
Cc: linux-wireless, Felix Fietkau, Daniel Golle,
Tomislav Požega, Mathias Kresin, Emil Karlson,
Fredrik Noring
Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> After looking at code I realized that my previous fix
> 95844124385e ("rt2x00: clear IV's on start to fix AP mode regression")
> was incomplete. We can still have wrong IV's after re-keyring.
> To fix that, clear up IV's also on key removal.
>
> Fixes: 710e6cc1595e ("rt2800: do not nullify initialization vector data")
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> tested-by: Emil Karlson <jekarl@iki.fi>
Patch applied to wireless-drivers.git, thanks.
14d5e14c8a6c rt2x00: clear up IV's on key removal
--
https://patchwork.kernel.org/patch/11111605/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-09-03 13:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-23 12:48 [PATCH 5.3] rt2x00: clear up IV's on key removal Stanislaw Gruszka
2019-08-27 8:30 ` Emil Karlson
2019-09-03 13:52 ` Kalle Valo
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).