After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 590644 - Trying to connect to a WPA2 / TLS secured network the connect button is greyed out
Trying to connect to a WPA2 / TLS secured network the connect button is greye...
Status: RESOLVED DUPLICATE of bug 719982
Product: NetworkManager
Classification: Platform
Component: nm-applet
Other All
: Normal major
: ---
Assigned To: Dan Williams
NetworkManager maintainer(s)
Depends on:
Reported: 2009-08-03 15:54 UTC by Dirk Hohndel
Modified: 2014-07-23 15:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

.xsession-errors (5.52 KB, text/plain)
2009-10-27 23:16 UTC, Christopher Covington

Description Dirk Hohndel 2009-08-03 15:54:34 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
Authentication: TLS
Identity: host/FQHN
User cert: <path to file>
CA cert: <path to file>
Private key: <path to file>
PK passwd

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

Actual results:
you can't connect

Expected results:
being able to click the connect button and connect to the network

Does this happen every time?

Other information:
this is version 0.7.1 as shipping with Fedora 11 x86/32
Comment 1 Dan Williams 2009-09-03 23:51:17 UTC
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.
Comment 2 Christopher Covington 2009-10-27 23:16:19 UTC
Created attachment 146384 [details]

.xsession-errors after unsuccessfully running networkmanager-applet WPA & WPA2.
Comment 3 Christopher Covington 2009-10-27 23:17:14 UTC
My pem private key file looks like it decodes fine with openssl. See also
Comment 4 Dan Williams 2009-10-28 19:53:19 UTC
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.
Comment 5 Christopher Covington 2009-10-30 13:14:33 UTC
I'm running nm-applet version 0.7.996 on Ubuntu Karmic. Any source or deb I could test with?
Comment 6 Christopher Covington 2009-11-13 15:56:50 UTC
Turns out I was using an expired certificate. For me then, the bug is really that NM provided insufficient feedback.
Comment 7 Tobias Mueller 2010-04-10 22:54:38 UTC
Reopening as per the last comment.

I feel we should open a new bug for that issue though.
Comment 8 Dan Williams 2014-07-23 15:47:17 UTC
Duping to the PKCS#11 bug, since that will end up fixing this.

*** This bug has been marked as a duplicate of bug 719982 ***