From: Jouni Malinen <j@w1.fi>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: mac80211 hardware encryption
Date: Mon, 7 Apr 2008 10:07:48 +0300 [thread overview]
Message-ID: <20080407070748.GM2025@jm.kir.nu> (raw)
In-Reply-To: <200804061844.14166.IvDoorn@gmail.com>
On Sun, Apr 06, 2008 at 06:44:14PM +0200, Ivo van Doorn wrote:
> After some more research I have a similar question for the RX path.
> The device will strip the IV out of the ieee80211 frame but provides
> the IV/EIV seperately in the descriptor.
>
> Would it be any added value to instead of setting the RX_FLAG_IV_STRIPPED
> flag the IV is reinserted into the frame, provide the IV/EIV seperately in
> struct ieee80211_rx_status, or simply set RX_FLAG_IV_STRIPPED and ignore
> the entire field?
Yes, I would highly recommend delivering IV/EIV to mac80211 so that
replay protection can be implemented properly. This is required if the
hardware/firmware does not have full implementation of replay protection
(including support for multiple access categories in case QoS is used).
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2008-04-07 7:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 17:31 mac80211 hardware encryption Ivo van Doorn
2008-04-06 16:44 ` Ivo van Doorn
2008-04-07 7:07 ` Jouni Malinen [this message]
2008-04-07 13:09 ` Johannes Berg
2008-04-07 13:34 ` Ivo van Doorn
2008-04-07 13:47 ` Johannes Berg
2008-04-07 14:10 ` Ivo van Doorn
2008-04-07 14:12 ` Johannes Berg
2008-04-07 14:26 ` Ivo van Doorn
2008-04-07 14:36 ` Johannes Berg
2008-04-07 14:45 ` Ivo van Doorn
2008-04-14 16:27 ` Ivo van Doorn
2008-04-14 18:39 ` Tomas Winkler
2008-04-14 21:07 ` Ivo van Doorn
2008-04-15 10:35 ` Johannes Berg
2008-04-15 15:17 ` Ivo van Doorn
2008-04-16 13:57 ` Johannes Berg
2008-04-17 10:14 ` Johannes Berg
2008-04-17 17:04 ` Ivo van Doorn
2008-04-15 15:55 ` Tomas Winkler
2008-04-16 6:15 ` 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=20080407070748.GM2025@jm.kir.nu \
--to=j@w1.fi \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).