linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "Ortwin Glück" <odi@odi.ch>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WEP and enc restricted
Date: Mon, 15 Sep 2008 01:24:08 -0400	[thread overview]
Message-ID: <1221456248.27102.43.camel@localhost.localdomain> (raw)
In-Reply-To: <48CD314C.40105@odi.ch>

On Sun, 2008-09-14 at 17:44 +0200, Ortwin Gl=C3=BCck wrote:
> Hi,
>=20
> I am pretty sure that the mac80211 code doesn't handle WEP with share=
d keys=20
> correctly. Using the ath9k driver on my MacBook I am unable to put th=
e driver=20
> into restricted mode (shared key). It stays in open mode. That is the=
 following=20
> command has no effect: iwconfig wlan0 enc restricted. I can also conf=
irm this=20
> when looking at the authentication packets that go over the air: they=
 are sent=20
> with the open flag, and not the shared key flag.

It looks like ieee80211_rx_mgmt_auth() in mlme.c should be cycling
through the various auth methods when it gets an "auth not supported"
response from the AP.  I wonder why that's not working in your case.
Can you put some printks in there and see if that code gets triggered
and if not, poke around a bit to see why?

> Surprisingly nowhere in the mac80211 code the ifsta->auth_alg is set =
to=20
> WLAN_AUTH_SHARED_KEY so far. The attached small patch does just that.=
 I am not=20
> 100% sure if that's the way to do it, so please review carefully.

It looks like it does get set from the SIWAUTH handler if you pass in
the right auth algs bits; but you're correct in that SIWENCODE won't se=
t
the auth alg.  The patch seems to be correct.

However, the submission format needs a few things: the signed-off-by
line, and the patch should be inlined rather than attached to make for
easier review.  Please see here:

http://linux.yyz.us/patch-format.html

Thanks!
Dan

> With this patch authentication works. The AP now denies association, =
but that is=20
> another problem.
>=20
> Cheers
>=20
> Ortwin
> plain text document attachment (patch.diff)
> --- wext.c.orig	2008-07-21 22:18:29.000000000 +0200
> +++ wext.c	2008-09-14 16:46:09.000000000 +0200
> @@ -929,6 +929,14 @@
>  	else
>  		idx--;
> =20
> +	if (sdata->vif.type =3D=3D IEEE80211_IF_TYPE_STA) {
> +		struct ieee80211_if_sta *ifsta =3D &sdata->u.sta;
> +		if (erq->flags & IW_ENCODE_OPEN)
> +			ifsta->auth_alg =3D WLAN_AUTH_OPEN;
> +		else if (erq->flags & IW_ENCODE_RESTRICTED)
> +			ifsta->auth_alg =3D WLAN_AUTH_SHARED_KEY;
> +	}
> +
>  	if (erq->flags & IW_ENCODE_DISABLED)
>  		remove =3D 1;
>  	else if (erq->length =3D=3D 0) {

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-09-15  5:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 15:44 WEP and enc restricted Ortwin Glück
2008-09-15  5:24 ` Dan Williams [this message]
2008-09-15  8:31   ` Ortwin Glück

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=1221456248.27102.43.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).