From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jkm@devicescape.com>
Cc: netdev <netdev@vger.kernel.org>, Jiri Benc <jbenc@suse.cz>
Subject: Re: 802.11/crypto questions
Date: Tue, 08 Aug 2006 13:35:22 +0200 [thread overview]
Message-ID: <44D876FA.5080605@sipsolutions.net> (raw)
In-Reply-To: <20060807172946.GI4702@instant802.com>
Jouni Malinen wrote:
> Depends on what exactly you mean with "on the fly". We have indeed
> changed between doing software and hardware crypto for some cases, e.g.,
> when enabling another BSS while one BSS is using static WEP (which would
> need default WEP keys in hwaccel) in one BSS, we may disable hwaccel for
> the receive case.
Yeah, that's basically what I was thinking of.
Also, if we add a monitor if, does it disable hw crypto so we can see
the undecrypted frames?
johannes
next prev parent reply other threads:[~2006-08-08 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 5:40 802.11/crypto questions Johannes Berg
2006-08-07 17:29 ` Jouni Malinen
2006-08-08 11:35 ` Johannes Berg [this message]
2006-08-08 15:57 ` Jouni Malinen
2006-08-08 16:09 ` Ivo van Doorn
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=44D876FA.5080605@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jbenc@suse.cz \
--cc=jkm@devicescape.com \
--cc=netdev@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).