From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3] cfg80211: rework key operation
Date: Wed, 15 Jul 2009 16:38:06 +0800 [thread overview]
Message-ID: <1247647086.3695.48.camel@debian> (raw)
In-Reply-To: <1247055774.24749.0.camel@johannes.local>
On Wed, 2009-07-08 at 20:22 +0800, Johannes Berg wrote:
> This reworks the key operation in cfg80211, and now only
> allows, from userspace, configuring keys (via nl80211)
> after the connection has been established (in managed
> mode), the IBSS been joined (in IBSS mode), at any time
> (in AP[_VLAN] modes) or never for all the other modes.
>
> In order to do shared key authentication correctly, it
> is now possible to give a WEP key to the AUTH command.
> To configure static WEP keys, these are given to the
> CONNECT or IBSS_JOIN command directly, for a userspace
> SME it is assumed it will configure it properly after
> the connection has been established.
This breaks wireless-tools for WEP with fullmac cards because "iwconfig
key" doesn't send the AUTH command. Is it expected?
Thanks,
-yi
> Since mac80211 used to check the default key in IBSS
> mode to see whether or not the network is protected,
> it needs an update in that area, as well as an update
> to make use of the WEP key passed to auth() for shared
> key authentication.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
next prev parent reply other threads:[~2009-07-15 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 11:13 [PATCH] cfg80211: rework key operation Johannes Berg
2009-07-08 11:30 ` [PATCH v2] " Johannes Berg
2009-07-08 12:22 ` [PATCH v3] " Johannes Berg
2009-07-15 8:38 ` Zhu Yi [this message]
2009-07-15 9:37 ` Johannes Berg
2009-07-15 14:43 ` Johannes Berg
2009-07-16 3:07 ` Zhu Yi
2009-07-16 8:41 ` Johannes Berg
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=1247647086.3695.48.camel@debian \
--to=yi.zhu@intel.com \
--cc=johannes@sipsolutions.net \
--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 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.