From: Johannes Berg <johannes@sipsolutions.net>
To: "Tobin C. Harding" <me@tobin.cc>, linux-wireless@vger.kernel.org
Subject: Re: WPA and WPA2
Date: Wed, 24 May 2017 09:40:51 +0200 [thread overview]
Message-ID: <1495611651.2665.9.camel@sipsolutions.net> (raw)
In-Reply-To: <20170524072750.GI8158@eros> (sfid-20170524_092758_235291_603981F2)
On Wed, 2017-05-24 at 17:27 +1000, Tobin C. Harding wrote:
> I am attempting to rewrite the ks7010 WEXT driver
> (drivers/staging/ks7010) to use the CFG80211 API.
Heh, I wasn't even aware of this driver yet.
> As I understand, first there was WEP.
Correct.
> Next we got a marketing term WPA which referred to 802.11i (which
> specified the protocols TKIP and CCMP, and also RSN).
No, technically WPA referred to a *draft* version of 802.11i, and used
(only?) TKIP - where WPA2 is equivalent to RSN, the published version
of 802.11i (now long rolled into the spec, of course), but WPA2 also
preferred CCMP and only used TKIP for compatibility, IIRC.
> WEP vs WPA
> ----------
>
> To add to my confusion the ks7010 code seemingly mixes up the use of
> WEP keys and WPA keys, to set both the WEP and the WPA keys the
> driver uses the same MIB requests? Yet throughout the code WEP keys
> and WPA keys are stored in separate structures (and treated
> differently).
>
> If WPA is enabled are not WEP keys superfluous?
Well, you can't really have both at the same time, but you can (and
probably should) support both.
> WPA vs WPA2
> -----------
>
> Were WPA version 1 and WPA version 2 marketing terms or do they
> differ?
See above. But at the level you're looking at, it's probably not really
all that relevant. To some extent, WPA1 is TKIP and WPA2 is CCMP, but
you don't really care since you just get keys with a cipher suite
identifier attached to them.
> ieee80211.h does not seem to mention WPA2 (and cfg80211.h mentions it
> once only in some comments) however, from cfg80211.h;
>
> * struct cfg80211_crypto_settings - Crypto settings
> * @wpa_versions: indicates which, if any, WPA versions are enabled
> * (from enum nl80211_wpa_versions)
>
> When using the CFG80211 API we do not need to worry about the
> WPA/WPA2 distinction?
This is only relevant for full-MAC devices, I think it's mostly used
for selecting the BSS?
> Can I drop all the WPA version 1 code from the driver?
>
> A little more information:
>
> The WEXT driver defines ciphers, from looking at ieee80211.h it seems
> that it uses WLAN_CIPHER_SUITE_XXX for WPA2 and for WPA it uses
>
> #define CIPHER_ID_WPA_NONE "\x00\x50\xf2\x00"
> #define CIPHER_ID_WPA_WEP40 "\x00\x50\xf2\x01"
> #define CIPHER_ID_WPA_TKIP "\x00\x50\xf2\x02"
> #define CIPHER_ID_WPA_CCMP "\x00\x50\xf2\x04"
> #define CIPHER_ID_WPA_WEP104 "\x00\x50\xf2\x05"
That's ... strange. The standard identifiers are
WLAN_CIPHER_SUITE_*, which are 00-0F-AC:n (with the same values for n
as above).
If the firmware wants them with MS OUI, then you'd probably have to
translate them.
All this wext code there looks really strange though.
Does this driver actually work with standard wpa_supplicant?
johannes
next prev parent reply other threads:[~2017-05-24 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 7:27 WPA and WPA2 Tobin C. Harding
2017-05-24 7:34 ` Tobin C. Harding
2017-05-24 16:44 ` Dan Williams
2017-05-24 18:06 ` Johannes Berg
2017-05-24 22:40 ` Tobin C. Harding
2017-05-25 17:45 ` Dan Williams
2017-05-28 21:30 ` Tobin C. Harding
2017-05-26 8:32 ` Johannes Berg
2017-05-24 22:43 ` Tobin C. Harding
2017-05-24 7:40 ` Johannes Berg [this message]
2017-05-24 10:13 ` Tobin C. Harding
2017-05-24 10:47 ` 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=1495611651.2665.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@tobin.cc \
/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).