All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ortwin Glück" <odi@odi.ch>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] Don't destroy authentication algorithm before	authenticating.
Date: Mon, 15 Sep 2008 18:00:54 +0200	[thread overview]
Message-ID: <48CE86B6.6080704@odi.ch> (raw)
In-Reply-To: <1221494039.3700.47.camel@johannes.berg>



Johannes Berg wrote:
> On Mon, 2008-09-15 at 17:50 +0200, Ortwin Gl=C3=BCck wrote:
>> reset_auth is called before each authentication try. So it should no=
t destroy
>> the auth_alg that was set before.
>>
>> NB: this may have side-effects with automatic algorithm selection if=
 AP responds=20
>> with alg not supported.
>=20
> This seems entirely wrong.
>=20
> Is your AP not capable of/configured to do open auth and _also_ doesn=
't
> reject the attempt? That is, the AP is just completely broken?

Well, I see that with other (binary) drivers it actively rejects such=20
authentication attempts. But with this driver it doesnt. The only diffe=
rence=20
that I can see from the packet logs is that mac80211 sends no probes be=
fore the=20
authentication, and that the sequence number is being reset. So maybe t=
hat keeps=20
this Netgear AP (yes it's crap) from rejecting. Or then it's something =
in ath9k=20
that causes the AP not to receive the packets in the first place.

Ortwin

--
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 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15 15:50 [PATCH 2/2] Don't destroy authentication algorithm before authenticating Ortwin Glück
2008-09-15 15:53 ` Johannes Berg
2008-09-15 16:00   ` Ortwin Glück [this message]
2008-09-15 16:04     ` Johannes Berg
2008-09-15 16:39       ` Ortwin Glück
2008-09-15 18:15         ` Johannes Berg
2008-09-15 19:02           ` Ortwin Glück
2008-09-15 20:49             ` Luis R. Rodriguez

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=48CE86B6.6080704@odi.ch \
    --to=odi@odi.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.