GNOME Bugzilla – Bug 630280
file chooser dialog box does not show certificate files
Last modified: 2016-05-30 10:20:51 UTC
When selecting WPA enterprise security for a new connection and subsequently trying to choose a certificate file from a directory: 1. If the directory is a subdirectory of ~/Desktop (whether in english or localised), then no files appear in file chooser, though they exist. Confirmed in two cases - see reference thread below. 2. If the directory is not a subdirectory of ~/Desktop, then in one case the files do appear (my case), in another they are reported as still not showing - see reference thread below. 3. In the 2nd case of (2) above, dragging the files from the nautilus folder window inside the file list of the nm-applet file chooser dialog, is reported to make the files appear and be selectable aftwerwards. This can be considered a temporary work-around. Again, see reference thread below. My *non-informed* guess -if behaviour #3 can be confirmed- is that when the file chooser dialog starts either some directory-contents structure is not initialised properly, or a relevant draw-contents action is not performed. I set the severity to "major" because from a user stand point this behaviour hinders the ability to perform the requested action. Reference thread: http://ubuntuforums.org/showthread.php?t=1576689 nm-applet version: 0.7.996 (my case) OS: Ubuntu 9.10 Karmic Koala (both cases)
Is there a chance you can attach any sample certificates that fail to show up in the file chooser? nm-applet has some validation to only show actual certificate files, and that code may need tweaking (though we're pretty confident that since 0.8.0 we've got it working well).
Created attachment 170796 [details] SAMPLE CERTIFICATES Contains some sample certificates extracted from my browser certificate store. Of these the .p12 failed to show up.
I rerun the test cases more carefully and what I see is that it is just the .p12 files that do not show up when opening the file chooser for a private key. The others appeared normally and also bogus certs did not show up, as expected. I also see from the reference thread (look at the attached images in OP's posts) that it was the .p12 files that could not see either. In a test run with just three bogus certs, when a single file is dragged and dropped to the file chooser box, all three appeared and remained there even when the current folder was changed and then came back or the file chooser was closed and then reopened (in the same `add new connection...' session). So the workaround reported by the OP appears to be valid; it can be also considered a bug because in my case it allowed to specify a bogus cert file.
PS: a. The test folders was one "inside" ~/Desktop, one "inside" ~/. b. I failed to reproduce the step #1 behaviour (cert not shown under ~/Desktop - shown under ~/ ); either the cert file was ok and could be seen in both locations or not and could not be seen in both, also. The non-able-to-reproduce observation may was related with drag-n-drop move or copy from source to dest; I did not keep exact notes then, so cannot really tell.
any news for this report?
This bug seems quite stale, but has just reoccurred for me on Xenial. Versions installed: ii network-manager 1.1.93-0ubuntu4 amd64 network management framework (daemon and userspace tools) ii network-manager-gnome 1.2.0-0ubuntu0.16.04.1 amd64 network management framework (GNOME frontend)
This is probably a duplicate of bug 763578.
(In reply to Beniamino Galvani from comment #7) > This is probably a duplicate of bug 763578. In that case, there should be a message printed by nm-c-e, when started from the terminal: (nm-connection-editor:2471): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed
Tested on my system (cannot comment for original submitter) and yes, I get that message from nm-c-e jammy@abc007470:~$ nm-connection-editor Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ** Message: Cannot save connection due to error: Initialising editor... ** Message: Cannot save connection due to error: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing (nm-connection-editor:19662): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed (nm-connection-editor:19662): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed (nm-connection-editor:19662): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed Thanks, looks like I just need to wait for the patch to filter through to the Ubuntu repos. For any other visitors who hit this, the workaround of dragging a cert from nautilus into the selection box for the key works great.
Thanks James, the lines (nm-connection-editor:19662): libnm-CRITICAL **: nm_utils_file_is_private_key: assertion 'out_encrypted == NULL || *out_encrypted == FALSE' failed indicate that your issue is bug 763578. I don't think that the original issue is the same issue here. (In reply to gzarkadas from comment #2) > Created attachment 170796 [details] > SAMPLE CERTIFICATES > > Contains some sample certificates extracted from my browser certificate > store. Of these the .p12 failed to show up. I am confused how to reproduce this issue and what the expected behavior is. There are three certificates. AUTHServersCertificationAuthority2008.der seems to work fine. $ openssl pkcs12 -info -in AUTHUsersCertificationAuthorityR3.p12 fails with an error. I also cannot select the certificate in the UI, but this certificate seems broken to me, thus it is not shown. Are you saying, this certificate is valid and should be shown? $ openssl pkcs12 -info -in cuzco-blackboard-com.p12 fails with an error too, but it can be selected in the UI at first, but later it appears to be invalid. I guess, for the certificate chooser, nm-c-e assumes the file is password protected and thus shows it. Later, verification fails because it cannot be decrypted. Whether the files are in ~, ~/Desktop or otherwise, doesn't seem to make a difference for me. So, I would say, the original bug of selecting p12 files is not reproducible anymore. Sorry for taking so long. Please reopen if you can reproduce with recent versions. With the example certificates there are some issues, the files seem invalid. If they are valid certificates that are supposed to work, the bug is not about the file-chooser, but about handling certain certificates in general. In this case, please open a bug with one certificate that is supposed to work, but does not.