Save... button deactivated, can't create WPA WPA2 Enterprise connection

2014-05-02 Thread Chuck Anderson
I've had this problem for awhile now (maybe the last year or 2,
certainly Fedora 20 and Fedora 19, and probably Fedora 18 as well).

When creating a new Wi-Fi connection:

Security: WPA  WPA2 Enterprise
Authentication: TLS
User certificate: file in .der format
CA certifcate: file in .der format
Private key: file in .pem format
Private key password: provided

The Save... button remains greyed out/deactivated, so there is no
way to save the connection.  This happens both when selecting a new
Wi-Fi network from the Gnome shell, as well as running
nm-connection-editor manually.

Is there a workaround so I can create the connection?

Thanks.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Save... button deactivated, can't create WPA WPA2 Enterprise connection

2014-05-02 Thread Dan Williams
On Fri, 2014-05-02 at 14:49 -0400, Chuck Anderson wrote:
 I've had this problem for awhile now (maybe the last year or 2,
 certainly Fedora 20 and Fedora 19, and probably Fedora 18 as well).
 
 When creating a new Wi-Fi connection:
 
 Security: WPA  WPA2 Enterprise
 Authentication: TLS
 User certificate: file in .der format
 CA certifcate: file in .der format
 Private key: file in .pem format
 Private key password: provided

Could you run nm-connection-editor from a terminal and see what output
it dumps when you type the private key password?

Next, could you provide the top few lines of the private key .pem file?
They should look something like this:

-BEGIN RSA PRIVATE KEY-
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,5FA2D6D6242C26D0

Feel free to obscure the salt at the end ofthe DEK-Info line, if that
line exists for you.

Dan

 The Save... button remains greyed out/deactivated, so there is no
 way to save the connection.  This happens both when selecting a new
 Wi-Fi network from the Gnome shell, as well as running
 nm-connection-editor manually.
 
 Is there a workaround so I can create the connection?
 
 Thanks.
 ___
 networkmanager-list mailing list
 networkmanager-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/networkmanager-list


___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Save... button deactivated, can't create WPA WPA2 Enterprise connection

2014-05-02 Thread Chuck Anderson
On Fri, May 02, 2014 at 02:32:01PM -0500, Dan Williams wrote:
 On Fri, 2014-05-02 at 14:49 -0400, Chuck Anderson wrote:
  I've had this problem for awhile now (maybe the last year or 2,
  certainly Fedora 20 and Fedora 19, and probably Fedora 18 as well).
  
  When creating a new Wi-Fi connection:
  
  Security: WPA  WPA2 Enterprise
  Authentication: TLS
  User certificate: file in .der format
  CA certifcate: file in .der format
  Private key: file in .pem format
  Private key password: provided
 
 Could you run nm-connection-editor from a terminal and see what output
 it dumps when you type the private key password?

$ nm-connection-editor

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi: 
802-11-wireless.ssid: property is missing

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi: 
802-11-wireless.ssid: property is missing

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi: 
802-11-wireless.ssid: property is missing

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi: 
802-11-wireless.ssid: property is missing

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): CRITICAL **: crypto_md5_hash: assertion 
'password_len  0' failed

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private key: 
1 private-key

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private key: 
1 private-key

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private key: 
1 private-key

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private key: 
1 private-key

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private key: 
1 private-key

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security

** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
Invalid Wi-Fi security


 Next, could you provide the top few lines of the private key .pem file?
 They should look something like this:
 
 -BEGIN RSA PRIVATE KEY-
 Proc-Type: 4,ENCRYPTED
 DEK-Info: DES-EDE3-CBC,5FA2D6D6242C26D0
 
 Feel free to obscure the salt at the end ofthe DEK-Info line, if that
 line exists for you.

-BEGIN RSA PRIVATE KEY-
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,

 Dan
 
  The Save... button remains greyed out/deactivated, so there is no
  way to save the connection.  This happens both when selecting a new
  Wi-Fi network from the Gnome shell, as well as running
  nm-connection-editor manually.
  
  Is there a workaround so I can create the connection?

So I now know what the problem was this time around.  The passphrase I
was using was incorrect.  Is there any way to provide user feedback
when this happens?

Thanks.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Save... button deactivated, can't create WPA WPA2 Enterprise connection

2014-05-02 Thread Dan Williams
On Fri, 2014-05-02 at 16:37 -0400, Chuck Anderson wrote:
 On Fri, May 02, 2014 at 02:32:01PM -0500, Dan Williams wrote:
  On Fri, 2014-05-02 at 14:49 -0400, Chuck Anderson wrote:
   I've had this problem for awhile now (maybe the last year or 2,
   certainly Fedora 20 and Fedora 19, and probably Fedora 18 as well).
   
   When creating a new Wi-Fi connection:
   
   Security: WPA  WPA2 Enterprise
   Authentication: TLS
   User certificate: file in .der format
   CA certifcate: file in .der format
   Private key: file in .pem format
   Private key password: provided
  
  Could you run nm-connection-editor from a terminal and see what output
  it dumps when you type the private key password?
 
 $ nm-connection-editor
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi: 
 802-11-wireless.ssid: property is missing
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi: 
 802-11-wireless.ssid: property is missing
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi: 
 802-11-wireless.ssid: property is missing
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi: 
 802-11-wireless.ssid: property is missing
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): CRITICAL **: crypto_md5_hash: assertion 
 'password_len  0' failed
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private 
 key: 1 private-key
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private 
 key: 1 private-key
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private 
 key: 1 private-key
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private 
 key: 1 private-key
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Error: couldn't verify private 
 key: 1 private-key
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 ** (nm-connection-editor:4150): WARNING **: Invalid setting Wi-Fi Security: 
 Invalid Wi-Fi security
 
 
  Next, could you provide the top few lines of the private key .pem file?
  They should look something like this:
  
  -BEGIN RSA PRIVATE KEY-
  Proc-Type: 4,ENCRYPTED
  DEK-Info: DES-EDE3-CBC,5FA2D6D6242C26D0
  
  Feel free to obscure the salt at the end ofthe DEK-Info line, if that
  line exists for you.
 
 -BEGIN RSA PRIVATE KEY-
 Proc-Type: 4,ENCRYPTED
 DEK-Info: DES-EDE3-CBC,
 
  Dan
  
   The Save... button remains greyed out/deactivated, so there is no
   way to save the connection.  This happens both when selecting a new
   Wi-Fi network from the Gnome shell, as well as running
   nm-connection-editor manually.
   
   Is there a workaround so I can create the connection?
 
 So I now know what the problem was this time around.  The passphrase I
 was using was incorrect.  Is there any way to provide user feedback
 when this happens?

Yeah, we've toyed with outlining fields that