From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>, Jouni Malinen <j@w1.fi>,
linux-wireless@vger.kernel.org, jirislaby@gmail.com,
mickflemm@gmail.com, mcgrof@qca.qualcomm.com,
ath5k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath5k: add support of HW encryption in management frames
Date: Tue, 04 Sep 2012 18:57:25 +0200 [thread overview]
Message-ID: <1346777845.3737.39.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <201209041855.13593.chunkeey@googlemail.com> (sfid-20120904_185524_891747_0BF21249)
On Tue, 2012-09-04 at 18:55 +0200, Christian Lamparter wrote:
> > By the way, current secured mesh requires the AES CMAC to be enabled.
> > But without enabling IEEE80211_HW_MFP_CAPABLE, the key cannot be added
> > since this cipher suite is considered not supported. But actually AES
> > CMAC can be done in software. Any work around on this?
> >
> I think you can override this by supplying your own custom set
> of available ciphers. This is done by setting
> hw.wiphy->cipher_suites
> hw.wiphy->n_cipher_suites
> during the initalization of the driver (i.e.: before
> ieee80211_register_hw(hw) is called).
Yes, that's the way you could do it, but my argument that it's pointless
still stands, so what good would it do?
johannes
next prev parent reply other threads:[~2012-09-04 16:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 9:34 [PATCH] ath5k: add support of HW encryption in management frames Chun-Yeow Yeoh
2012-08-31 6:58 ` Adrian Chadd
2012-08-31 15:24 ` Yeoh Chun-Yeow
2012-09-03 19:24 ` Adrian Chadd
2012-09-04 1:03 ` Yeoh Chun-Yeow
2012-09-04 8:11 ` Johannes Berg
2012-09-04 9:28 ` Yeoh Chun-Yeow
2012-09-04 9:31 ` Johannes Berg
2012-09-04 10:22 ` Jouni Malinen
2012-09-04 11:21 ` Yeoh Chun-Yeow
2012-09-04 11:25 ` Yeoh Chun-Yeow
2012-09-04 11:35 ` Johannes Berg
2012-09-04 16:41 ` Yeoh Chun-Yeow
2012-09-04 16:54 ` Johannes Berg
2012-09-05 6:52 ` Yeoh Chun-Yeow
2012-09-04 16:55 ` Christian Lamparter
2012-09-04 16:57 ` Johannes Berg [this message]
2012-09-05 7:16 ` Jouni Malinen
2012-09-05 7:31 ` Yeoh Chun-Yeow
2012-09-05 8:03 ` Jouni Malinen
2012-09-07 3:51 ` Yeoh Chun-Yeow
2012-09-09 1:47 ` Adrian Chadd
2012-09-10 13:13 ` Kalle Valo
2012-09-10 15:11 ` Yeoh Chun-Yeow
2012-09-11 6:46 ` Nick Kossifidis
2012-09-11 9:42 ` Yeoh Chun-Yeow
2012-09-11 15:05 ` Nick Kossifidis
2012-09-11 15:51 ` Yeoh Chun-Yeow
2012-09-11 16:06 ` Nick Kossifidis
2012-09-11 16:07 ` Nick Kossifidis
2012-09-11 16:20 ` Yeoh Chun-Yeow
2012-09-11 16:30 ` Adrian Chadd
2012-09-11 16:36 ` Nick Kossifidis
2012-09-11 16:39 ` Johannes Berg
2012-09-11 17:31 ` Christian Lamparter
2012-09-11 17:48 ` Nick Kossifidis
2012-09-05 7:11 ` Jouni Malinen
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=1346777845.3737.39.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=chunkeey@googlemail.com \
--cc=j@w1.fi \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=mickflemm@gmail.com \
--cc=yeohchunyeow@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).