GNOME Bugzilla – Bug 590644
Trying to connect to a WPA2 / TLS secured network the connect button is greyed out
Last modified: 2014-07-23 15:47:17 UTC
Please describe the problem:
Entering the following information should allow me to connect to the network (and works fine when killing NM and manually starting wpa_supplicant) but the dialogue has the connect button greyed out:
Wireless Security: WPA & WPA2 Enterprise
User cert: <path to file>
CA cert: <path to file>
Private key: <path to file>
Steps to reproduce:
1. go to a site with WPA2 / TLS secured network
2. type in the required information in the dialogue box
3. watch it grey out the connect button
you can't connect
being able to click the connect button and connect to the network
Does this happen every time?
this is version 0.7.1 as shipping with Fedora 11 x86/32
Can you attach the contents of your ~/.xsession-errors file when you try this? What format are your certificates in, and are you sure your private key password really decrypts the private key itself? You can verify this with:
openssl rsa -in <path to pk file> -text
and type in your password. If you use a DSA key, use "openssl dsa" instead of "openssl rsa".
If it's a pkcs12 file, use:
openssl pkcs12 -in <path to PK file> -info
and enter your private key password.
Created attachment 146384 [details]
.xsession-errors after unsuccessfully running networkmanager-applet WPA & WPA2.
My pem private key file looks like it decodes fine with openssl. See also https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/447145.
There are two problems fixed in NM 0.7.2 (already fixed in 0.8 master) that will likely solve your issue. Since you're using Fedora, would you mind trying out this update which includes the fix?
you can, as root:
yum --enable-repo=updates-testing update NetworkManager
and it should grab them for you.
I'm running nm-applet version 0.7.996 on Ubuntu Karmic. Any source or deb I could test with?
Turns out I was using an expired certificate. For me then, the bug is really that NM provided insufficient feedback.
Reopening as per the last comment.
I feel we should open a new bug for that issue though.
Duping to the PKCS#11 bug, since that will end up fixing this.
*** This bug has been marked as a duplicate of bug 719982 ***