From: "Tobin C. Harding" <me@tobin.cc>
To: linux-wireless@vger.kernel.org
Subject: Re: WPA and WPA2
Date: Wed, 24 May 2017 17:34:59 +1000 [thread overview]
Message-ID: <20170524073459.GJ8158@eros> (raw)
In-Reply-To: <20170524072750.GI8158@eros>
On Wed, May 24, 2017 at 05:27:50PM +1000, Tobin C. Harding wrote:
> Hi,
>
> I am attempting to rewrite the ks7010 WEXT driver (drivers/staging/ks7010)
> to use the CFG80211 API.
>
> I am reading 802.11 Wireless Networks - Matthew S. Gast for reference.
>
> I have some confusion regarding WEP/WPA/WPA2/RSN, ciphers, keys and
> ie's?
>
> As I understand, first there was WEP. Next we got a marketing term WPA
> which referred to 802.11i (which specified the protocols TKIP and
> CCMP, and also RSN).
>
> 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).
Oh, I just got why there is only one MIB request type - there are only
one set of keys used by the target
DOT11_WEP_DEFAULT_KEY_VALUE1 = 0x13020101,
DOT11_WEP_DEFAULT_KEY_VALUE2 = 0x13020102,
DOT11_WEP_DEFAULT_KEY_VALUE3 = 0x13020103,
DOT11_WEP_DEFAULT_KEY_VALUE4 = 0x13020104,
removing 'WEP' from the defines removes the confusion here :)
> If WPA is enabled are not WEP keys superfluous?
>
> WPA vs WPA2
> -----------
>
> Were WPA version 1 and WPA version 2 marketing terms or do they differ?
>
> 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? 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"
>
> FYI ieee80211.h has
>
> #define WLAN_OUI_MICROSOFT 0x0050f2
>
> Thanks for taking the time to read this mail, any suggestions most
> appreciated.
>
> thanks,
> Tobin.
next prev parent reply other threads:[~2017-05-24 7:35 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 [this message]
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
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=20170524073459.GJ8158@eros \
--to=me@tobin.cc \
--cc=linux-wireless@vger.kernel.org \
/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).