Hi all
I just stumpled accross the very same issue
At the moment i run network manager version:
network-manager-gnome 1.2.6-0ubuntu0.16.04.4
so it should be fixed -> but I was unable to select my key..
I exported the key following and old HowTo to get wlan running in a
linux pc as the company is running windows domains with wpa2 enterprise
..
pfx=my_exported_cert.pfx
openssl pkcs12 -in $pfx -out cacert.pem -cacerts -nokeys
openssl pkcs12 -in $pfx -out cert.pem -clcerts -nokeys
openssl pkcs12 -in $pfx -out key.pem -nocerts
that generated all files required -> prior to that I had to request a
new cert with exportable private keys on a windows pc ..
key resulting key.pem was:
file key.pem
key.pem: ASCII text
with header of:
Bag Attributes
localKeyID: 01 00 00 00
Microsoft CSP Name: Microsoft Strong Cryptographic Provider
friendlyName:
le-Auth_Ses_ClientUser_KNAPPD-0485e131-adac-48b4-bd80-417a8495e1f3
Key Attributes
X509v3 Key Usage: 80
-----BEGIN ENCRYPTED PRIVATE KEY-----
And I think that was the issue with this key:
After converting the key to RSA format it worked for me and network
manager detected it !.
openssl rsa -in key.pem -out secure.key.key
file secure.key.key
secure.key.key: PEM RSA private key
And now i an running my WPA2 enterprise WLAN :)
regards
Chewie
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1575614
Title:
[SRU]Can't select p12 secret key for TLS auth for 802.1X
authentication
Status in NetworkManager:
Fix Released
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager-applet package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
Fix Released
Status in network-manager-applet source package in Xenial:
Fix Released
Bug description:
[Impact]
Users cannot select TLS certificate when connecting to a network that
requires TLS type 802.1X authentication
[Test case]
STR:
1. Click on Connections icon in status panel
2. Click on Edit connections
3. Select Wired connection
4. Go to 802.1x tab
5. Check the Use 802.1X checkbox
6. Choose TLS
7. Click on Secret key button
8. In file chooser navigate to the folder where key is located and try to
select key file - the list is empty
For wifi connection:
1. Click on Connections icon in status panel
2. Click on Edit connections
3. Select Wi-Fi connection
4. Go to Wi-Fi Security tab
5. Select WPA & WPA2 Enterprise in the drop-down list
6. Choose TLS
7. Click on (None) next to Private key
8. In file chooser navigate to the folder where key is located and try to
select key file - the list is empty
[Regression Potential]
The fix is quite straight forward and the possibility of causing regression
is limited.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1575614/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
