All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Jouni Malinen <j@w1.fi>
Cc: Vasanthakumar Thiagarajan <vasanth@atheros.com>,
	linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
	Jouni.Malinen@atheros.com
Subject: Re: [PATCH] [RFC] mac80211: Disable HT negotiation with TKIP/WEP as pairwise cipher
Date: Fri, 19 Dec 2008 10:30:39 -0500	[thread overview]
Message-ID: <20081219153039.GC4041@tuxdriver.com> (raw)
In-Reply-To: <20081219145616.GA12018@jm.kir.nu>

On Fri, Dec 19, 2008 at 04:56:16PM +0200, Jouni Malinen wrote:
> On Fri, Dec 19, 2008 at 09:28:22AM -0500, John W. Linville wrote:
> > Are there perhaps any broken APs out there that support such a
> > configuration?  I would hate to prevent users from connecting simply
> > out of blind obedience to the standard.
> 
> The goal of this change is _not_ to prevent connection, it only disables
> HT association, i.e., legacy (11a/g/b) is still available.

It was pointed-out to me that allowing TKIP/HT connections exposes
the user to unnecessary security risks as well.

Please resubmit with a changelog that a) makes it clear that
connections are still possible, just not HT; and b) "TKIP is not
updated to new security needs (e.g., related to some block ack details)
since it is not allowed mode, i.e., those extensions are only defined
for CCMP" (quoted from Jouni).

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

      reply	other threads:[~2008-12-19 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19 13:10 [PATCH] [RFC] mac80211: Disable HT negotiation with TKIP/WEP as pairwise cipher Vasanthakumar Thiagarajan
2008-12-19 13:17 ` Johannes Berg
2008-12-19 14:25   ` Vasanthakumar Thiagarajan
2008-12-19 14:28 ` John W. Linville
2008-12-19 14:33   ` Vasanthakumar Thiagarajan
2008-12-19 14:42     ` John W. Linville
2008-12-19 14:52       ` Richard Farina
2008-12-19 14:56   ` Jouni Malinen
2008-12-19 15:30     ` John W. Linville [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=20081219153039.GC4041@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Jouni.Malinen@atheros.com \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vasanth@atheros.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 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.