Re: What is needed for NetworkManager and WPA2 Enterprise?

[Paul Menzel <pmenzel molgen mpg de>]

Dear Andrew,


Thank you for your reply.


On 25.09.19 12:27, Andrew Zaborowski wrote:

> On Wed, 25 Sep 2019 at 11:43, Paul Menzel <pmenzel molgen mpg de> wrote:
> > Could you please talk to the NetworkManager folks, what you need? I
> > created the issue *Extend D-Bus API for iwd and WPA2 Enterprise* in
> > their GitLab instance [2] for that.
>
> I replied to that issue but provisioning EAP networks other than
> through the config files is not currently on IWD's todo list.  You
> didn't really explain your use case.  The logic is that the user
> shouldn't have to touch that configuration, it should be enough for
> them or their admin to drop the network's configuration file into
> /var/lib/iwd.  There is specific code in the NM iwd-backend to make
> sure no extra NM-side configuration is required after this is done
> correctly.
>
> Note that IWD config files currently contain paths to other files,
> specifically the certificates and private keys.  There is intention to
> allow our config files to directly encode the contents of those files
> instead, so you network admin can generate just that one file or
> provide a way for you to generate it.  We also do already have a way
> to use mac/iphone-compatible network config files.

There are self-managed devices. In our case these are scientists using 
the Eduroam net. It was possible to configure such a network before 
using the GNOME WiFi dialog, and I think it should continue to be supported.

Also it looks like, the password is stored in plain text in the iwd 
configuration file (in some examples).


Kind regards,

Paul