Summary: | client certificate authentication disabled (KIO::TCPSlaveBase::selectClientCertificate under #if 0), causes handshake error | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Ury Danko <urydanko> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | a.samirh78, adawit, adjam7, kde, kdelibs-bugs, kevin.kofler, rasasi78, rdieter, than |
Priority: | NOR | ||
Version: | 5.48.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Bug Depends on: | |||
Bug Blocks: | 178806 |
Description
Ury Danko
2008-07-29 18:18:10 UTC
I don't see TLS* cipher configuration in Konqueror at all That's because client cert authentication is completely disabled in KDE 4, KIO::TCPSlaveBase::selectClientCertificate is under #if 0. This also prevents us Fedora packagers from using the web interface for our build system (Koji). I can confirm this bug, it's still there in KDE 4.1.0 and it's obvious to see why (just look at the "#if 0"ed function). As for:
> I don't see TLS* cipher configuration in Konqueror at all
it should be there under "crypto", but that dialog is very buggy as well (placeholder texts all over the place, lists not being filled properly), but that's a separate bug. But the configuration won't help you much because the code to authenticate isn't there in the first place.
Is this still the case in the current version of KDE (v4.6.2 and up) ? Yes, the whole selectClientCertificate function is still stubbed out (with a childish "#if 0 //hehe", I don't find this funny at all), even in master. In addition, a client certificate cannot be configured because the whole certificate KCM was removed. (The KDE 4 port was very buggy and instead of fixing it, somebody just removed it.) There's a new one now under https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/show/kio/kssl/kcm but it doesn't allow configuring client certificates. (It's also not shown in Konqueror's settings.) This is an upstream Qt issue since KDE 4.x now relies on Qt's SSL libraries. See https://bugreports.qt-project.org/browse/QTBUG-1565. The problem seems to have been addressed in the upcoming Qt 5.4: https://codereview.qt-project.org/#change,85113 Unfortunately that means the entire KDE 4.x release is going to go without a feature that was present in KDE 3. :( |