iwd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>,
	Emil Velikov <emil.l.velikov@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: WPA3 SAE passphrase limitation
Date: Mon, 5 Dec 2022 13:38:42 -0600	[thread overview]
Message-ID: <9ac1b980-eea4-bcc2-a7cb-c6727731ee6e@gmail.com> (raw)
In-Reply-To: <6c0e45693e254dd8dda4d07a51896bab855a6324.camel@gmail.com>

Hi James,

>> About the only thing we can do is 'assume' WPA3 when:
>> 1. The user entered a non-conforming passphrase, and
>> 2. The current connection candidate is a WPA3-only AP,
>> 3. Connection succeeded
> 
> There is also the case of network profiles which we know even less
> about compared to agent requests. We could allow <8 character
> passphrases and just force WPA3 for these profiles too... but its still
> a rather weird side effect having a short passphrase force WPA3.
> 

This isn't only about < 8 chars.  It is also about allowing UTF8 passphrases, 
which is kinda desirable.

I would think the same restrictions would apply to saved profiles:
1. non-compliant passphrase
2. PSK setting must not be set
3. transition disable indication set.

If the above 3 are met, then we would allow this and the network would be 
treated as WPA3-only.

Regards,
-Denis

  reply	other threads:[~2022-12-05 19:38 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
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 [this message]
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=9ac1b980-eea4-bcc2-a7cb-c6727731ee6e@gmail.com \
    --to=denkenz@gmail.com \
    --cc=emil.l.velikov@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.com \
    /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).