Summary: | SSL KCM doesn't save any added certificates | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Elias Probst <mail> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fbrunnerreg, fetzt_doch, kdelibs-bugs, mailbox.tec, mpyne, registrace, sudhir, t.schmittlauch |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/kio/d06e40bc1e84391640fc56a4c5ba252eaa9dcc6d | Version Fixed In: | 5.31 |
Description
Elias Probst
2015-01-17 11:52:31 UTC
It looks like this fails when ~/.local/share/kssl/userCaCertificates doesn't exist. Neither the parent directory kssl nor userCaCertificates existed here. After creating it manually, I was able to add custom CA certs successfully. Confirmed for Kubuntu 15.10 Creating ~/.local/share/kssl/userCaCertificates manually fixes this. Same issue here with Kubuntu 16.04.1 LTS Creating the directory ~/.local/share/kssl/userCaCertificates did the trick. I think this is actually a bug in KIO; the cert saving/loading is actually implemented at kio/src/core/ksslcertificatemanager.cpp in the addCertificate() member function. I've opened a review request for a potential fix at https://phabricator.kde.org/D4060 Git commit d06e40bc1e84391640fc56a4c5ba252eaa9dcc6d by Michael Pyne. Committed on 11/01/2017 at 02:10. Pushed by mpyne into branch 'master'. kssl: Ensure user certificate directory has been created before use. The KSSL KCM (in kdelibs4support) fails to save imported certificates to the user certificate store, unless the user store directory is manually created by the user first. Fix by ensuring the directory is created before trying to save user certs. Differential Revision: https://phabricator.kde.org/D4060 FIXED-IN: 5.31 M +2 -2 src/core/ksslcertificatemanager.cpp https://commits.kde.org/kio/d06e40bc1e84391640fc56a4c5ba252eaa9dcc6d *** Bug 376402 has been marked as a duplicate of this bug. *** |