From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>, "Tobin C. Harding" <me@tobin.cc>,
linux-wireless@vger.kernel.org
Subject: Re: WPA and WPA2
Date: Wed, 24 May 2017 20:06:40 +0200 [thread overview]
Message-ID: <1495649200.20833.1.camel@sipsolutions.net> (raw)
In-Reply-To: <1495644240.12939.3.camel@redhat.com> (sfid-20170524_184417_597726_14DB4F2B)
Just a small correction:
On Wed, 2017-05-24 at 11:44 -0500, Dan Williams wrote:
>
> For RSN, they are 1 = PMK, 2 = GMK, 3 = GMK2, 4 seems unused.
PTK and GTK, and in theory you could have more than two GTKs but that's
not usually done.
> Because WEXT is pretty convoluted, I woudn't necessarily try to
> translate what eg ks_wlan_set_encode_ext() is doing directly to
> cfg80211, but to understand how the firmware interface works and then
> just write the cfg80211 code to the firmware interface.
>
> Basically, you have the following modes:
>
> a) open, no encryption
> b) WEP encryption (4 possible WEP keys, each either 40 or 104 bits)
> c) WPA/RSN (PMK and GMK are computed by wpa_supplicant and supplied
> to you, just need to send to firmware)
Again, PTK/GTK :)
> And to answer Johannes, this firmware looks much more fullmac than
> softmac; BSS selection seems left up to the firmware. You just send
> it a "connect with these parameters" command (HIF_INFRA_SET_REQ)
> including channels, SSID, BSSID, mode, etc and it does everything.
Yeah. Makes sense then.
johannes
next prev parent reply other threads:[~2017-05-24 18:06 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 [this message]
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=1495649200.20833.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--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).