From: Vasanthakumar Thiagarajan <vasanth@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Jouni Malinen <Jouni.Malinen@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [PATCH] [RFC v2] mac80211: Scale down to non-HT association with TKIP/WEP as pairwise cipher
Date: Mon, 22 Dec 2008 13:40:50 +0530 [thread overview]
Message-ID: <20081222081050.GA3500@localhost.localdomain> (raw)
In-Reply-To: <1229928585.3087.1.camel@johannes>
On Mon, Dec 22, 2008 at 12:19:45PM +0530, Johannes Berg wrote:
> > + case IW_AUTH_CIPHER_PAIRWISE:
> > + if (sdata->vif.type == NL80211_IFTYPE_STATION) {
> > + if (data->value & (IW_AUTH_CIPHER_WEP40 |
> > + IW_AUTH_CIPHER_WEP104 | IW_AUTH_CIPHER_TKIP))
> > + sdata->u.sta.flags |=
> > + IEEE80211_STA_TKIP_WEP_USED;
> > + else
> > + sdata->u.sta.flags &=
> > + ~IEEE80211_STA_TKIP_WEP_USED;
> > + }
> > + break;
>
> Can't we check
> the key algorithm for the pairwise key associated with the AP's sta_info
> directly in _send_assoc?
AP's sta_info will not have the negotiated pirwise cipher before association.
Vasanth
next prev parent reply other threads:[~2008-12-22 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 6:31 [PATCH] [RFC v2] mac80211: Scale down to non-HT association with TKIP/WEP as pairwise cipher Vasanthakumar Thiagarajan
2008-12-22 6:49 ` Johannes Berg
2008-12-22 7:25 ` Vasanthakumar Thiagarajan
2008-12-22 8:10 ` Vasanthakumar Thiagarajan [this message]
2008-12-22 8:45 ` 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=20081222081050.GA3500@localhost.localdomain \
--to=vasanth@atheros.com \
--cc=Jouni.Malinen@Atheros.com \
--cc=Vasanth.Thiagarajan@Atheros.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 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).