From: Lars George <lars.george@biotronik.com>
To: "connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: Next Connman version and OWE support?
Date: Wed, 17 Nov 2021 07:18:36 +0000 [thread overview]
Message-ID: <FRYP281MB1071B616037CC5361DD75CACEB9A9@FRYP281MB1071.DEUP281.PROD.OUTLOOK.COM> (raw)
Hello everybody,
First of all thanks for the great work with Connman.
I saw that Connman now also supports SAE (WPA3), but this is currently only available in the master branch. Are there any plans of releasing the current changes in the near future?
It would also be great if OWE (Opportunistic Wireless Encryption) would be supported at some point. Connman would need to identify it as ‘none’ type security and when connecting the key_mgmt=OWE is needed (at least when using wpa_supplicant). The information about this can be found in the Information Element data of the BSS in the AKM Suite List (see IEEE Std 802.11 chapter 9.4.2.25 RSNE). OWE has suite type 18.
When parsing the Information Element is already implemented in Connman (I am not yet familiar with the code) the usage of the IEEE80211w could also be read from it. The Management Frame Protection Required (IEEE80211w=2) and Management Frame Protection Capable can be found in the RSN capabilities (9.4.2.25.4 RSN capabilities - Bits 6 and 7). Currently this is only hard coded set within Connman when connecting to WPA3-SAE as this is required there and needs to be optional (IEEE80211w=1) for the transition mode.
Kind regards
Lars
biotronik.com<https://www.biotronik.com>
Follow us on Twitter<https://twitter.com/biotronik_news> and LinkedIn<https://www.linkedin.com/company/biotronik>
[Logo]
________________________________
BIOTRONIK SE & Co. KG
Woermannkehre 1, 12359 Berlin, Germany
Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501
Vertreten durch ihre Komplementärin:
BIOTRONIK MT SE
Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 118866 B
Geschäftsführende Direktoren: Prof. Dr. Hanns-Peter Knaebel (Vorsitzender), Dr. Daniel Bühler, Dr. Thomas Kraft, Stephan Schulz-Gohritz
________________________________
This e-mail and the information it contains including attachments are confidential and meant only for use by the intended recipient(s); disclosure or copying is strictly prohibited. If you are not addressed, but in the possession of this e-mail, please notify the sender immediately and delete the document.
next reply other threads:[~2021-11-17 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 7:18 Lars George [this message]
2021-11-17 8:57 ` Next Connman version and OWE support? Marcel Holtmann
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=FRYP281MB1071B616037CC5361DD75CACEB9A9@FRYP281MB1071.DEUP281.PROD.OUTLOOK.COM \
--to=lars.george@biotronik.com \
--cc=connman@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).