From: Ariel D'Alessandro <firstname.lastname@example.org> To: Daniel Wagner <email@example.com> Cc: firstname.lastname@example.org, email@example.com, Sven.Dembianny@bshg.com Subject: Re: [RFC connman v1 1/1] gsupplicant: Add support for WPA3-Personal Date: Thu, 5 Aug 2021 08:15:27 -0300 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hi Daniel, On 8/5/21 3:07 AM, Daniel Wagner wrote: > Hi Ariel, > > On Wed, Aug 04, 2021 at 06:23:14PM -0300, Ariel D'Alessandro wrote: >> Hi all, Daniel: >> >> WPA3 support has been recently added to connman (wpa_supplicant). As >> we've been discussing on a previous thread, this only supports >> WPA3-Personal-only mode. >> >> This RFC patchset adds support for WPA3-Personal transition mode, which >> supports both WPA2-Personal (PSK) and WPA3-Personal (SAE). >> >> Based on the AP accepted key management protocols, connman configures >> wpa_supplicant as follows: >> >> * WPA3-Personal-only mode: key_mgmt="SAE" ; ieee80211w=2 >> * WPA3-Personal transition mode: key_mgmt="SAE WPA-PSK" ; ieee80211w=1 >> >> This patch applies cleanly on top of current master branch (commit >> e36a38d8). >> >> I'd like to hear any thoughts you might have about this. >> For reference, see wpa_supplicant configuration . > > This looks good. If no one speaks up I am going to apply it. Sounds good. > > Daniel > > ps: we have a new mailing list (firstname.lastname@example.org). The old one > was shutdown. Thanks for pointing that out! Ariel
next prev parent reply other threads:[~2021-08-05 11:15 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com> 2021-08-05 6:07 ` Daniel Wagner 2021-08-05 11:15 ` Ariel D'Alessandro [this message] 2021-09-09 11:10 ` Ariel D'Alessandro 2021-09-13 6:27 ` Daniel Wagner [not found] ` <firstname.lastname@example.org> 2021-08-05 6:07 ` [RFC connman v1 1/1] gsupplicant: Add support for WPA3-Personal transition mode Daniel Wagner
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 \ --email@example.com \ --firstname.lastname@example.org \ --cc=Sven.Dembianny@bshg.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC connman v1 1/1] gsupplicant: Add support for WPA3-Personal' \ /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
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).