From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Srinivas Dasari <dasaris@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, jouni@codeaurora.org
Subject: Re: [PATCH v2] ieee80211: Increase the PMK maximum length to 64 bytes
Date: Wed, 07 Feb 2018 21:21:34 +0100 [thread overview]
Message-ID: <1518034894.3124.9.camel@sipsolutions.net> (raw)
In-Reply-To: <5A7B54E9.8070805@broadcom.com> (sfid-20180207_203508_852301_520027C6)
On Wed, 2018-02-07 at 20:35 +0100, Arend van Spriel wrote:
> On 2/7/2018 5:20 PM, Srinivas Dasari wrote:
> > This is needed to cover the case of DPP with the NIST P-521 and
> > brainpoolP512r1 curves which derive a PMK that is longer than the
> > previously used limit.
>
> So how are driver supposed to deal with this longer PMK. Maybe if you
> could elaborate on what DPP stands for in this context it would become
> more clear.
device provisioning protocol, I guess? But longer curves and longer PMK
is kinda obvious, whichever way that ends up getting used.
> Can we stick with PMK_MAX_LEN or does it need to be more
> fine-grained per use-case? If existing drivers only support 48 bytes PMK
> and trust nl80211 code to check that limit it may screw them up. Not?
Yeah I'm concerned about this too - and regardless of that issue, we
probably need those drivers that do support it to advertise support for
the new curves, and then allow the longer PMK length only for those that do?
johannes
next prev parent reply other threads:[~2018-02-07 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 16:20 [PATCH v2] ieee80211: Increase the PMK maximum length to 64 bytes Srinivas Dasari
2018-02-07 19:35 ` Arend van Spriel
2018-02-07 20:21 ` Johannes Berg [this message]
2018-02-10 10:32 ` Jouni Malinen
2018-02-10 20:26 ` 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=1518034894.3124.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=dasaris@codeaurora.org \
--cc=jouni@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.