Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] hostapd: remove use of ieee80211_msg_wep_frame_unknown_key
Date: Wed, 15 Aug 2007 18:50:11 -0700	[thread overview]
Message-ID: <20070816015011.GT1415@jm.kir.nu> (raw)
In-Reply-To: <1187174759.3998.8.camel@johannes.berg>

On Wed, Aug 15, 2007 at 12:45:59PM +0200, Johannes Berg wrote:
> On Tue, 2007-08-14 at 20:35 -0700, Jouni Malinen wrote:
> > However, this was causing
> > interoperability issues with some client implementations and the code
> > was eventually commented out and this was only used to update a dot11
> > MIB counters. Consequently, I did not see much point in integrating it
> > into hostapd and we might as well just remove the TODO item completely
> > from hostapd.

> I'm not sure whether it'd be worth it going forward anyway, with WEP
> deployments hopefully going down.

I don't think we can enable the original behavior of disassociating a
station based on use of incorrect key index since it can cause problems
with commonly used clients (well, clients that were commonly used four
years ago ;-) and there are also potential issues with opening yet
another DoS problem. If needed, we could have a MIB counter for the
errors updated, but I'm not too concerned about not having this
available.

-- 
Jouni Malinen                                            PGP id EFC895FA

      reply	other threads:[~2007-08-16  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 21:29 [PATCH] hostapd: remove use of ieee80211_msg_wep_frame_unknown_key Johannes Berg
2007-08-15  3:35 ` Jouni Malinen
2007-08-15 10:45   ` Johannes Berg
2007-08-16  1:50     ` Jouni Malinen [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=20070816015011.GT1415@jm.kir.nu \
    --to=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --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