Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: John Linville <linville@tuxdriver.com>,
	Samuel Ortiz <sameo@linux.intel.com>, Jouni Malinen <j@w1.fi>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: implement wext key handling
Date: Mon, 11 May 2009 16:09:22 +0200	[thread overview]
Message-ID: <1242050962.29777.12.camel@johannes.local> (raw)
In-Reply-To: <1242049846.28322.12.camel@localhost.localdomain>

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

On Mon, 2009-05-11 at 09:50 -0400, Dan Williams wrote:

> I modified the meaning of RESTRICTED/OPEN a few years ago to control the
> WEP auth mode, for a few reasons...  First, some fullmac drivers already
> used it to mean WEP auth mode.  Second, there was no other mechanism to
> control WEP auth mode at the time, and there were a lot of Shared Key
> installations around.  Third, WE-18/WPA was nowhere near being landed,
> and it was only supported by one driver (hostap), and it was the only
> thing that would plausibly support WEP auth mode via SIWAUTH.  Fourth,
> only hostap and maybe airo really implemented the refuse-non-encoded
> anyway.

But didn't update the header file ;)

> TBH, SK is nice because it tells you that the WEP key is wrong
> *immediately*, and the only reason NM doesn't use SK by default (and
> then fall back to OS) like the original Mac Airport drivers did is that
> WEXT simply cannot return reliable association error information.

Hah. Well, we could have that now, but I suspect SK is no longer common
enough to put a lot of work into it.

> But in the end, we still need a mechanism with WEXT to be able to set SK
> auth when associating.

We still have that, with WE18, in IW_AUTH_80211_AUTH_ALG. And mac80211
never actually supported _setting_ the WEP auth mechanism with
RESTRICTED/OPEN, only _getting_ that information.

johannes


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

  reply	other threads:[~2009-05-11 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 11:54 [PATCH] cfg80211: implement wext key handling Johannes Berg
2009-05-11 13:50 ` Dan Williams
2009-05-11 14:09   ` Johannes Berg [this message]
2009-05-11 22:16     ` Hin-Tak Leung
2009-05-11 22:40       ` Dan Williams
2009-05-11 23:21         ` Hin-Tak Leung
2009-05-12  6:32       ` 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=1242050962.29777.12.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sameo@linux.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