From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH] carl9170: connect to 11w protected networks
Date: Sun, 02 Sep 2012 23:48:23 +0200 [thread overview]
Message-ID: <1346622503.10113.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <E1T89yV-0007Cn-JT@debian64.localnet> (sfid-20120902_151319_118701_3604D3F3)
On Sun, 2012-09-02 at 14:25 +0200, Christian Lamparter wrote:
> Previously, it was not possible to connect to
> networks which requires 11w to be supported by
> the stations.
>
> While the documentation hints that there's some
> hardware support for offloading MFP "decryption",
> this simple implementation relies on the mac80211
> stack to do the actual crypto operations.
Maybe we need to clarify the documentation...
The problem with MFP is that now unicast management frames are encrypted
with CCMP. If the device has HW crypto on RX or TX, it may not implement
it correctly due to the different header munging needed for management
frames over data frames.
You should verify that unicast management frames are properly encrypted
and decrypted by the hardware (or punted to software on RX like you do
on TX). The danger is that the hardware corrupts CCMP encrypted RX mgmt
frames and software can't recover.
johannes
next prev parent reply other threads:[~2012-09-02 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 12:25 [PATCH] carl9170: connect to 11w protected networks Christian Lamparter
2012-09-02 21:48 ` Johannes Berg [this message]
2012-09-02 22:53 ` Christian Lamparter
2012-09-02 23:18 ` Johannes Berg
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=1346622503.10113.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.