On 19/11/18 1:48 pm, Samuel Sieb wrote:
On 11/18/18 1:42 PM, Stephen Morris wrote:
> I also created a new user and it behaved similarly but slightly
> differently. When I logged in with the new user I made the mistake of
> not changing the default so it logged into Gnome, and when Gnome
> started Networkmanager had a definition for ethernet and my wifi even
> though they had not been explicitly set up, and the wifi definition
> had the correct password for my router as the network was connected.
Ethernet is normally automatic, no configuration required.
By default, NetworkManager stores the password in a keys-* file. I've
never tried making a connection not global so I don't know what would
happen in that case. I assume that somewhere along the way with your
KDE tests, the password got stored. When you used Gnome, it would
have the password already.
From my experience, at least under KDE, the password is
stored in
keys-* files if the wifi-security enty in Networkmanager is set to
"Store password for all users (not encrypted)" and as the option says
the password is in plain text in the keys file. If the option is changed
to "Store password for this user only (encrypted)" the keys file is
removed and the encrypted password is stored in kwallet. The original
issue with the password being blank instead of masked in the wifi
definition surfaced when investigating why at KDE start up, after I was
prompted for the kwallet password, I was being prompted for the wifi
password before the network would activate. Installing pam-kwallet has
now stopped the prompting for the kwallet password every time I start KDE.
> I logged out of Gnome and logged into KDE, and went into the
> networkmanager wifi definition and deliberately set the wifi password
> to an incorrect entry from the correct entry that the definition had.
> The incorrect entry was not retained and neither was the correct
> entry blanked out like in the original issue, or something was
> overwriting the incorrect entry with the correct one.
It would seem that something isn't working quite right between KDE and
NetworkManager.
My assumption was it was a Networkmanager is when changing the password
setting from "encrypted" to "not encrypted" caused the password to be
retained, and then changing the setting from "not encrypted" back to
"encrypted" continued to retain the password in the Networkmanager wifi
configuration.
regards,
Steve
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org