From: Johannes Berg <johannes@sipsolutions.net>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Dan Williams <dcbw@redhat.com>, linux-wireless@vger.kernel.org
Subject: Re: WPA and WPA2
Date: Fri, 26 May 2017 10:32:16 +0200 [thread overview]
Message-ID: <1495787536.2572.2.camel@sipsolutions.net> (raw)
In-Reply-To: <20170524224014.GC2319@eros>
On Thu, 2017-05-25 at 08:40 +1000, Tobin C. Harding wrote:
> On Wed, May 24, 2017 at 08:06:40PM +0200, Johannes Berg wrote:
> > 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.
>
> Excuse my ignorance but why do you say PTK and GTK here?
Well, you said that it was doing TKIP MMIC in software, so you need the
TK to do that :) It seemed unlikely to be received from the firmware.
Also, I know that Dan meant PTK/GTK - a "GMK" doesn't exist at all.
> Who generates the transient keys, hardware, firmware or software? Is
> this device specific or is there a *normal* way?
Dan explained this well.
> From the nomenclature in the WEXT driver I thought the driver
> supplied the master keys to the firmware and transient keys were
> generated at the firmware layer or lower.
Seems unlikely, but it seems also very based on WEP which didn't have a
concept of "master" and "transient" keys.
johannes
next prev parent reply other threads:[~2017-05-26 8:32 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 [this message]
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=1495787536.2572.2.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).