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 698575 - Save WPA2 ca certificate somewhere
Save WPA2 ca certificate somewhere
Status: RESOLVED DUPLICATE of bug 689818
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
0.9.x
Other Linux
: Normal enhancement
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-04-22 14:43 UTC by Morse
Modified: 2015-06-15 08:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Morse 2013-04-22 14:43:36 UTC
A certificate for WPA2 enterprise is a part of a network setup, yet user should store the file somewhere by himself, with the possibility of deleting it accidentally, after which the connection will become unusable (no errors will be reported, just fail to connect).

Also, if user is creating a connection "for everybody" it's not correct to store crt file inside user's home folder, as it's part of the system now. Yet, user doesn't have a permission to write anywhere outside his home folder, which can make it impossible for him to create a WPA2ent connection "for everybody", even if he's allowed to do it by polkit.
Comment 1 Dan Williams 2013-04-22 19:58:03 UTC
The longer-term fix for this is to require the user to import the certificate to a system-level certificate store, and then NM just tells the supplicant to use the system certificate store for validation.

The shorter term fix might involve copying certificates the user picks to some directory in ~.  At least in SELinux, certain directories in ~ are tagged to allow processes like wpa_supplicant to read from and so if you don't put the certificate there, then things fail due to permissions errors.
Comment 2 Thomas Haller 2015-06-15 08:46:07 UTC
I'm closing this as a duplicate of bug 689818.

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