iwd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Emil Velikov <emil.l.velikov@gmail.com>, iwd@lists.linux.dev
Subject: Re: WPA3 SAE passphrase limitation
Date: Mon, 5 Dec 2022 10:58:47 -0600	[thread overview]
Message-ID: <d2df3b8c-2b0e-b587-bd04-4892e4e84f5c@gmail.com> (raw)
In-Reply-To: <CACvgo51HZVDcmvHiaZK3XFJyp6LUGRFEM+G=5j1--av=XWni+w@mail.gmail.com>

Hi Emil,

On 12/5/22 10:19, Emil Velikov wrote:
> Greetings list,
> 
> I was playing around with a router using WPA3 Personal (only) +
> CCMP-128 (AES) and noticed something odd. Namely: the 8 character
> limitation imposed by WPA2 is enforced with WPA3/SAE.
> 

What 8 character limitation?

> Whenever I try to use such a passphrase (via iwctl) I get an error
> "Argument format is invalid".
> 

Refer to crypto_passphrase_is_valid() for what we consider a valid passphrase.

> I realise it's not the best practice but the exact same router just
> works with my Android Pixel phone.
> 
> Would anyone be interested in fixing this bug? Alternatively any
> pointers where the validation happens would be appreciated.
> 

What bug?  In theory the passphrase can be anything for SAE-only networks, but 
since there are plenty of cases where hybrid networks exist, managing separate 
SAE and non-SAE passphrases becomes tricky.

Regards,
-Denis

Regards,
-Denis

  reply	other threads:[~2022-12-05 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 16:19 WPA3 SAE passphrase limitation Emil Velikov
2022-12-05 16:58 ` Denis Kenzior [this message]
2022-12-05 17:44   ` Emil Velikov
2022-12-05 18:48     ` Denis Kenzior
2022-12-05 19:01       ` James Prestwood
2022-12-05 19:38         ` Denis Kenzior
2022-12-06 12:39       ` Emil Velikov
2022-12-06 17:57         ` Denis Kenzior

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=d2df3b8c-2b0e-b587-bd04-4892e4e84f5c@gmail.com \
    --to=denkenz@gmail.com \
    --cc=emil.l.velikov@gmail.com \
    --cc=iwd@lists.linux.dev \
    /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).