FS#49295 - [nm-connection-editor] Cannot add a private key when configuring a wpa enterprise connection

Attached to Project: Arch Linux
Opened by Domenico Iezzi (nomore66201) - Wednesday, 11 May 2016, 11:47 GMT
Last edited by Jan de Groot (JGC) - Saturday, 19 August 2017, 21:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
In nm-connection-editor it's not possible to add a private key when configuring a wpa enterprise connection ( with TLS authentication ).
The GtkFileChooserDialog will not find files *.der *.pem *.p12 *.key, althought they are there with right permission, and it found them in previous versions.
When launching nm-connection-editor from terminal, the following output is printed while opening the GtkFileChooserDialog to select the private key:

(nm-connection-editor:2471): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed

(nm-connection-editor:2471): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed

(nm-connection-editor:2471): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed

(nm-connection-editor:2471): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed

(nm-connection-editor:2471): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed

(nm-connection-editor:2471): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed

(nm-connection-editor:2471): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed

Additional info:
* package version(s)
networkmanager 1.2.0-3
nm-connection-editor 1.2.0-1
network-manager-applet 1.2.0-1
* config and/or log files etc.


Steps to reproduce:
1) Launch nm-connection editor and add a new wifi connection (or connect to a wpa enterpise network)
2) in the WiFi-Security tab select "Wpa & Wpa2 Enterprise" Security and then TLS as authentication
3) click on Private Key field
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 19 August 2017, 21:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  Upstream marked as fixed
Comment by Domenico Iezzi (nomore66201) - Thursday, 12 May 2016, 07:49 GMT
This bug persists with latest nm update.

networkmanager-1.2.2-1
nm-connection-editor-1.2.2-1
network-manager-applet-1.2.2-1
libnm-glib-1.2.2-1
Comment by Domenico Iezzi (nomore66201) - Friday, 13 May 2016, 07:16 GMT
The bug was filed also in the upstream bug tracker:
https://bugzilla.gnome.org/show_bug.cgi?id=763578

Loading...