Network Manager doesn't use 802.1x password entered in GUI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
This is a bug that seems to constantly re-surface across multiple versions in Ubuntu, and I've seen it in other distributions as well.
Scenario:
I want to enable 802.1x on a wired (*not* wireless), ethernet connection. I enter my identity, my computer cert, my ca cert, my private key file, and my password for my private key.
What doesn't work:
I confirm the password works by using openssl. NetworkManager does not save the password. When I am asked to re-enter it, the connection fails. I look in syslog, and it complains about the private key password being blank.
Workaround:
Open the file:
/etc/NetworkMan
Example:
$> vim /etc/NetworkMan
Add the field:
private-
Example:
private-
Save the file.
Attempt to re-connect. (and it worked for me).
Look in Network Manager UI, the password seems to now be stored.
Expected behavior:
Entering the password in the GUI works (i.e, it is saved to the file, or at least used temporarily when connecting, either way - the latter would be more secure)
Additionally, this whole thing is pretty lame, because Network Manager restricts you to using an encrypted private key, but this is dumb, because the password is then stored in a globally readable file in plaintext. Or you can decide to not save a password, and enter every time in a gui that fails to use the password you type in.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.
ProcVersionSign
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 21 17:52:44 2016
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-11-21 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
default via 10.0.50.1 dev eno1 proto static metric 100
10.0.50.0/23 dev eno1 proto kernel scope link src 10.0.50.207 metric 100
10.0.254.32 via 10.0.50.1 dev eno1 proto dhcp metric 100
169.254.0.0/16 dev eno1 scope link metric 1000
IwConfig:
lo no wireless extensions.
eno1 no wireless extensions.
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
RfKill:
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-
Wired connection 1 fcbffec0-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
eno1 ethernet connected /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.2.0 connected started full enabled enabled enabled enabled enabled
information type: | Public → Public Security |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.