public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>, Jouni Malinen <j@w1.fi>
Subject: Re: [RFC/RFT] cfg80211: implement wext key handling
Date: Mon, 11 May 2009 15:58:42 +0200	[thread overview]
Message-ID: <1242050322.29777.8.camel@johannes.local> (raw)
In-Reply-To: <1242050250.28322.16.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

On Mon, 2009-05-11 at 09:57 -0400, Dan Williams wrote:
> On Sat, 2009-05-09 at 20:16 +0200, Johannes Berg wrote:
> > Move key handling wireless extension ioctls from mac80211 to cfg80211
> > so that all drivers that implement the cfg80211 operations get wext
> > compatibility.
> > 
> > Note that this drops the SIOCGIWENCODE ioctl. This means that iwconfig
> > will no longer report "Security mode:open" or "Security mode:restricted"
> > for mac80211. However, what we displayed there (the authentication algo
> > used) was actually wrong -- linux/wireless.h states that this setting is
> > meant to differentiate between "Refuse non-encoded packets" and "Accept
> > non-encoded packets". Dropping SIOCGIWENCODE also means that you can no
> > longer display the key currently in use. We believe this is a misfeature
> > in wireless extensions and unneeded; cfg80211 currently provides no way
> > to implement it.
> 
> Does this mean inability to display current WEP key index, or just the
> key that the card is supposedly using?  Seeing the index may be
> important, but the ability to pull the actual key out of the card was
> not consistently implemented across WEXT drivers.

I actually added that back, seems people want to be able to pull the key
out... I'll address your other email separately.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

      reply	other threads:[~2009-05-11 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-09 18:16 [RFC/RFT] cfg80211: implement wext key handling Johannes Berg
2009-05-11 13:57 ` Dan Williams
2009-05-11 13:58   ` Johannes Berg [this message]

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=1242050322.29777.8.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=j@w1.fi \
    --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