linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dan Williams <dcbw@redhat.com>,
	linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH v2] p54: connect to 11w protected networks
Date: Fri, 7 Sep 2012 18:10:18 +0200	[thread overview]
Message-ID: <201209071810.18821.chunkeey@googlemail.com> (raw)
In-Reply-To: <1347033342.4256.28.camel@jlt4.sipsolutions.net>

On Friday 07 September 2012 17:55:42 Johannes Berg wrote:
> On Fri, 2012-09-07 at 17:47 +0200, Christian Lamparter wrote:
> > On Friday 07 September 2012 14:17:14 Johannes Berg wrote:
> > > On Tue, 2012-09-04 at 16:54 +0200, Johannes Berg wrote:
> > >
> > > If you want this for your driver, I'll commit this:
> > > 
> > > http://p.sipsolutions.net/ea2e3dbe980f5db8.txt
> > 
> > Won't this totally disable the crypto offload
> > capabilities in AP mode?
> 
> Yes, though we could add an nl80211 attribute that
> allows hostapd to tell us, and then if it did tell
> us we could know and do the right thing here.

Well, if we want to do the right thing here, then I
guess we should go for another alternative: a rxkey
manager of some sorts. So, we delete keys from the
firmware context once MFP comes into the game.

This method also has another advantage that with
a proper manager we can use the key usage statistics
and upload only the most-used keys into the firmware
context (most/all? p54 firmwares have usually 4-8 key
slots in total, which is not always enough).
 
> > I sort of prefer the nohwcrypt switch as it won't
> > interfere with running user setups as much (so we
> > don't burden systems like that weird telekom
> > streamin-box (Vision S100 - it's name I think)
> > that came with a p54pci minipci card and are
> > now used for different purposes by some.
> 
> I guess it would make sense then to give hostapd the ability to tell us?
> 
> It's up to you. I don't need 11w, nor do I have p54 hardware, nor does
> it matter much to me ... :)
Let's save that task for a rainy day :-D.

Regards,
	Chr

  reply	other threads:[~2012-09-07 16:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-02 13:22 [PATCH] p54: connect to 11w protected networks Christian Lamparter
2012-09-02 21:48 ` Johannes Berg
2012-09-04 13:19   ` [PATCH v2] " Christian Lamparter
2012-09-04 14:15     ` Johannes Berg
2012-09-04 14:33       ` Dan Williams
2012-09-04 14:37         ` Johannes Berg
2012-09-04 14:54           ` Johannes Berg
2012-09-07 12:17             ` Johannes Berg
2012-09-07 15:47               ` Christian Lamparter
2012-09-07 15:55                 ` Johannes Berg
2012-09-07 16:10                   ` Christian Lamparter [this message]
2012-09-07 16:15                     ` Johannes Berg
2012-09-07 16:26                       ` Christian Lamparter
     [not found]   ` <201209071825.13588.chunkeey@googlemail.com>
     [not found]     ` <1347035277.4256.33.camel@jlt4.sipsolutions.net>
2012-09-07 17:01       ` Christian Lamparter
2012-09-07 17:09         ` Johannes Berg
2012-09-07 17:28           ` 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=201209071810.18821.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --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 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).