From: Johannes Berg <johannes@sipsolutions.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: Michael Buesch <mb@bu3sch.de>,
netdev@vger.kernel.org, yi.zhu@intel.com,
ipw2100-admin@linux.intel.com
Subject: Re: ieee80211 and devices which decrypt in hardware
Date: Thu, 14 Sep 2006 09:51:28 +0200 [thread overview]
Message-ID: <1158220288.2936.16.camel@ux156> (raw)
In-Reply-To: <450887B9.7080308@gentoo.org>
On Wed, 2006-09-13 at 18:35 -0400, Daniel Drake wrote:
> + /* If the device does decryption but leaves the IV in place then we:
> + * need to kill it. */:
> + if (!can_be_decrypted && (fc & IEEE80211_FCTL_PROTECTED)):
> + hdrlen += 4;:
That might work, unless there are devices that leave the protected bit
set but do strip the IV/ICV...
johannes
next prev parent reply other threads:[~2006-09-14 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 2:51 ieee80211 and devices which decrypt in hardware Daniel Drake
2006-09-13 14:27 ` Michael Buesch
2006-09-13 22:35 ` Daniel Drake
2006-09-13 22:43 ` Daniel Drake
2006-09-14 7:51 ` Johannes Berg [this message]
2006-09-14 15:25 ` Michael Buesch
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=1158220288.2936.16.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=dsd@gentoo.org \
--cc=ipw2100-admin@linux.intel.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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).