Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Ortwin Glück" <odi@odi.ch>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: Support iwconfig enc restricted with WEP
Date: Mon, 15 Sep 2008 18:06:10 +0200	[thread overview]
Message-ID: <1221494770.3700.57.camel@johannes.berg> (raw)
In-Reply-To: <1221494210.3700.50.camel@johannes.berg> (sfid-20080915_175726_992604_5474600F)

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

On Mon, 2008-09-15 at 17:56 +0200, Johannes Berg wrote:

> > +	if (sdata->vif.type == IEEE80211_IF_TYPE_STA) {
> > +		struct ieee80211_if_sta *ifsta = &sdata->u.sta;
> > +		if (erq->flags & IW_ENCODE_OPEN) {
> > +			printk("wext: open\n");
> > +			ifsta->auth_alg = WLAN_AUTH_OPEN;
> > +		}
> > +		else if (erq->flags & IW_ENCODE_RESTRICTED) {
> > +			printk("wext: shared key\n");
> > +			ifsta->auth_alg = WLAN_AUTH_SHARED_KEY;
> > +
> 
> Come to think of it, since we already fall back from open to shared-key
> when the AP rejects, why would we want to support this at all? The
> semantics aren't well defined enough to support it _properly_, that is
> have it change the ifsta->auth_algs variable, and touching this variable
> as you're doing in these two patches is just plain wrong since it can be
> changed underneath (yes, you're removing the automatic changing, but
> that's totally wrong).

Then again, I suppose you _can_ actually implement this, but in terms of
which authentication algorithms are allowed, something like:

if (erq->flags & RESTRICTED)
	ifsta->auth_algs = SHARED;
else
	ifsta->auth_algs = OPEN | SHARED | LEAP;

johannes

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

      reply	other threads:[~2008-09-15 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15 15:47 [PATCH 1/2] mac80211: Support iwconfig enc restricted with WEP Ortwin Glück
2008-09-15 15:49 ` Johannes Berg
2008-09-15 15:56 ` Johannes Berg
2008-09-15 16:06   ` 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=1221494770.3700.57.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=odi@odi.ch \
    /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