All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dembianny, Sven (GDE-EDSO)" <Sven.Dembianny@bshg.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
	"connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: Re: [PATCH 1/1] gsupplicant: Add MFP support for WPA2
Date: Tue, 16 May 2023 10:40:29 +0000	[thread overview]
Message-ID: <20230516104029.GA2062332@rbgwcw0248.bsh.corp.bshg.com> (raw)
In-Reply-To: <4b9a0754ab29428fb95b53a65c399925@bshg.com>

> > >>>
> > >>> Shall we also consider the "WPA-PSK" case in the same way?
> > >
> > > As to my understanding, MFP requires SHA256.
> > >
> > >>
> > >> I prefer we remove wpa_supplicant support from ConnMan and you start
> > >> using iwd ;)
> > >>
> > >> And I am only half joking since this part of wpa_supplicant is such a mess.
> > >> Whatever key management they introduce next will turn into your next
> > >> problem and compatibility issues. I am running independent SSIDs in
> > >> my home network to deal with end consumer device since they use a
> > >> wpa_supplicant and management software that is too dumb.
> > >>
> > >> With iwd the WiFi protocol is in one daemon and not split between two
> > >> daemons.
> > >
> > > Unfortunately in our case we are tied to wpa_supplicant because of chip
> > vendor specifications.
> > 
> > that is horrible. What is missing in nl80211 that you need wpa_supplicant? I am
> > really curious about that.
> 
> You can find the patches on wpa_supplicant from chip vendor in cypress-hostap_2_9-1-2022_0321.tar.gz, included in driver package:
> 
> https://community.infineon.com/gfawx74859/attachments/gfawx74859/WiFiBluetoothLinux/2314/4/cypress-fmac-v5.10.9-2022_0331.zip
> 
> No idea, if Wi-Fi chip will also work with iwd without adaptions.
> 
> Best regards, Sven
Hi Marcel,

sorry there was connman@lists.linux.dev missing in first mail.

any update here?
Unfortunately we can't solve the vendor dependencies, but I want to get
rid of
manual updates of the patch for every connman release.

Asking chip vendor for iwd support is all I could do at the moment. We
are planning to switch to iwd, but this needs alignment with supplier.

Best regards, Sven

      reply	other threads:[~2023-05-16 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 15:08 [PATCH 0/1] Add WPA2-MFP Support Dembianny, Sven (GDE-EDSO)
2022-04-25 15:08 ` [PATCH 1/1] gsupplicant: Add MFP support for WPA2 Dembianny, Sven (GDE-EDSO)
2022-04-26 14:19   ` Ariel D'Alessandro
2022-04-26 14:46     ` Marcel Holtmann
2022-04-27  7:20       ` Dembianny, Sven (GDE-EDSO)
2022-04-27 12:45         ` Marcel Holtmann
2022-05-09  7:46           ` Dembianny, Sven (GDE-EDSO)
2023-05-16 10:40             ` Dembianny, Sven (GDE-EDSO) [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:
  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=20230516104029.GA2062332@rbgwcw0248.bsh.corp.bshg.com \
    --to=sven.dembianny@bshg.com \
    --cc=ariel.dalessandro@collabora.com \
    --cc=connman@lists.linux.dev \
    --cc=marcel@holtmann.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.