Bug 341885 - User added SSL Certificate are lost when system settings is quit
Summary: User added SSL Certificate are lost when system settings is quit
Status: REPORTED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_ssl (other bugs)
Version First Reported In: 5.1.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs
URL: http://youtu.be/fbSzxdbN1e8
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-14 16:59 UTC by Sudhir Khanger
Modified: 2021-03-09 07:29 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sudhir Khanger 2014-12-14 16:59:18 UTC
I added a self-signed certificate to SystemSettings>Network and when I restarted system settings the certificate was gone.

Please see the video http://youtu.be/fbSzxdbN1e8

Reproducible: Always

Steps to Reproduce:
1. Add cert to SystemSettings>Network, apply and quit
2. Restart systemsettings and check if cert is still there
3.

Actual Results:  
Cert is lost when SystemSettings is quit
Comment 1 William Boren 2014-12-22 15:15:36 UTC
Hello, I'm a google code-in student with a task of bugtriaging.

Which version of Fedora and Plasma are you running?
Comment 2 Sudhir Khanger 2014-12-22 15:36:05 UTC
Hi William,

I was using Fedora 21 and Plasma 5.1.1 on the machine. I am back on KDE 4 for time being. You can see the video as a proof of the problem.

https://copr.fedoraproject.org/coprs/dvratil/plasma-5/
Comment 3 fetzt_doch 2015-12-04 21:54:41 UTC
I can absolutely confirm this for a freshly installed KUbuntu 15.10.

I can add my own CA-cert, it will then show up under user-added certificates. Once you hit "apply", close kcm_ssl and open it again the certificate is gone.

Why is this unconfirmed for a whole year?
Comment 4 fetzt_doch 2015-12-04 22:22:38 UTC
Duplicates Bug 342958. Workaround given there works.
Comment 5 Justin Zobel 2021-03-09 07:29:36 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.