Version: (using Devel) OS: Linux Installed from: Compiled sources KSSLD::setRule() uses the certificate's digest as the name of a KConfigGroup (kssld.cpp:108). This leads to a crash in kssld if the last byte of the digest is 0x1d as this is used as some (stringlist?) separator in kconfigini.cpp:294. I just happened to stumble upon this bug when connecting to some router that had a certificate that triggered this bug. I don't see a straightforward way to fix it so I can't provide a patch. A "clean" way might be to use rule.certificate().digest().toHex() as the groupname instead - but that would kill compatibility with old config files. Just a thought: it might do unexpected things if the digest contains [ or ] as well.
CCing maelcum as I don't know if I assigned the right product and/or he's reading the konq-bugs mailinglist.
Talked to ahartmetz and we agreed that this should be fixed in kconfig. KConfig should be able to handle binary data as section headers as well and shouldn't fail on special separator characters.
SVN commit 914920 by ahartmetz: Don't use binary group names for kssld/ksslcertificatemanager, they break KConfig. Included is a kconfig_update script to delete the old config file. BUG:178229 M +3 -0 CMakeLists.txt A kssl/ksslcertificatemanager.upd A kssl/ksslcertificatemanager.upd.sh M +3 -3 misc/kssld/kssld.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=914920