archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <>
To: Lars George <>
Cc: "" <>
Subject: Re: Next Connman version and OWE support?
Date: Wed, 17 Nov 2021 09:57:52 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <FRYP281MB1071B616037CC5361DD75CACEB9A9@FRYP281MB1071.DEUP281.PROD.OUTLOOK.COM>

Hi Lars,

> 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 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 ( 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.

frankly, I think you are better served switching to iwd as backend and ditching wpa_supplicant. I doubt that it makes sense to copy the logic of OWE and OWE transition mode to ConnMan. I think it will be really complicated for OWE transition mode and a big mess. The wpa_supplicant APIs are not really meant for this kind of handling. And in iwd you have this all handled internally. No extra work needed.



      reply	other threads:[~2021-11-17  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  7:18 Lars George
2021-11-17  8:57 ` Marcel Holtmann [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Next Connman version and OWE support?' \

* 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).