From: Hong Liu <hong.liu@intel.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Jouni Malinen <j@w1.fi>, Michael Wu <flamingice@sourmilk.net>,
Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/5] mac80211: fix key restricted/open display
Date: Thu, 22 Mar 2007 11:43:45 +0800 [thread overview]
Message-ID: <1174535025.9000.25.camel@devlinux-hong> (raw)
In-Reply-To: <1174260946.8053.20.camel@localhost.localdomain>
On Mon, 2007-03-19 at 07:35, Dan Williams wrote:
> On Sun, 2007-03-18 at 09:45 -0700, Jouni Malinen wrote:
> > WE-18 introduced IW_AUTH_80211_AUTH_ALG and that should be used if user
> > space wants to explicitly select which 802.11 authentication algorithm
> > is to be used. Please let the IW_ENCODE_OPEN/RESTRICTED misuse die.
>
> Obviously we want it to die. But the better solution is to make apps
> that care about "exclude unencrypted", which there are few, use
> ENCODEEXT and keep OPEN/RESTRICTED be what most of the old drivers
> expect it to be; the selector for OS/SK. Then clean up all the double
> meanings with cfg80211 and call it day.
>
> Dan
As far as mac80211 is concerned, I think the patch is not needed.
mac80211 has done what it needed to do through the SIOC{S/G}IWAUTH
interface.
It seems the fix should be in userspace app, iwconfig should use the
SIOC{S/G}IWAUTH interface and resort to IW_ENCODE_RESTRICTED if it wants
to maintain the compatibility with old drivers.
Thanks,
Hong
next prev parent reply other threads:[~2007-03-22 3:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 3:28 [PATCH 3/5] mac80211: fix key restricted/open display Hong Liu
2007-03-16 17:28 ` Michael Wu
2007-03-17 3:46 ` Dan Williams
2007-03-17 3:57 ` Michael Wu
2007-03-17 4:38 ` Dan Williams
2007-03-17 4:57 ` Michael Wu
2007-03-17 17:23 ` Dan Williams
2007-03-18 16:45 ` Jouni Malinen
2007-03-18 23:35 ` Dan Williams
2007-03-22 3:43 ` Hong Liu [this message]
2007-03-23 18:27 ` Jiri Benc
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=1174535025.9000.25.camel@devlinux-hong \
--to=hong.liu@intel.com \
--cc=dcbw@redhat.com \
--cc=flamingice@sourmilk.net \
--cc=j@w1.fi \
--cc=jbenc@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).