From: Sven Eckelmann <sven@narfation.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AuthSAE rekeying issues with ATH9K
Date: Tue, 18 Oct 2016 11:39:04 +0200 [thread overview]
Message-ID: <2697074.077QYVH3MI@bentobox> (raw)
In-Reply-To: <8a879fb0730946b5a771dfdcacbd3258@nldataex01.ad.fugro.com>
On Montag, 18. Juli 2016 11:45:06 CEST Stam, Michel [FINT] wrote:
[...]
> It is on the top of my todo list, will get to it hopefully today, or
> tomorrow.
Seems like this topic ended here. So lets poke a little bit :)
There was just a patch (ok, lets call it workaround/hack) released by open-
mesh.com [1]. It is used in their setup to detect key cache problems and work
around them.
Maybe this can also be relevant for this problem here. The patch was used with
IBSS RSN but could also be helpful here.
The patch itself has (at least) one big problem. It is using some mac80211
internals in ath_key_config_iter to make sure that the uploaded keys were
actually programmed in the hardware. Without this check the keys could end up
in the lower slots and thus break all connections.
So this patch could be a starting point for someone who wants to add a
workaround which is acceptable by upstream.
Kind regards,
Sven
[1] https://lkml.kernel.org/r/20161018083552.28592-1-a at unstable.cc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20161018/4c8cdf5c/attachment.pgp
prev parent reply other threads:[~2016-10-18 9:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 12:32 [ath9k-devel] AuthSAE rekeying issues with ATH9K Stam, Michel
2016-07-11 9:53 ` Stam, Michel
2016-07-13 20:39 ` Adrian Chadd
2016-07-13 20:41 ` Adrian Chadd
2016-07-13 20:45 ` Adrian Chadd
2016-07-14 9:12 ` Stam, Michel
2016-07-14 8:34 ` Stam, Michel
2016-07-14 18:58 ` Adrian Chadd
2016-07-14 19:47 ` Stam, Michel
2016-07-14 20:10 ` Adrian Chadd
2016-07-15 20:29 ` Adrian Chadd
2016-07-18 11:45 ` Stam, Michel
2016-10-18 9:39 ` Sven Eckelmann [this message]
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=2697074.077QYVH3MI@bentobox \
--to=sven@narfation.org \
--cc=ath9k-devel@lists.ath9k.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox