Version: (using KDE KDE 3.5.3) Installed from: Debian testing/unstable Packages If, when accessing an HTTPS server, all the encryption methods that the webserver is willing to support are disabled in Konqueror's config, then the default "Can't connect" error message is displayed. Since this error does not indicate that HTTPS failed, it is not clear to the user that (s)he should review the security settings in Settings/Configure Konqueror/Crypto. Konqueror should give a different error if HTTPS encryption negotation fails, inviting the user to review the settings, and perhaps listing the methods the webserver is willing to use.
reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374508
A Gentoo user¹ ran into this problem as well, having SSL2 disabled and trying to reach https://cacert.org. Reproducible. [1] https://bugs.gentoo.org/show_bug.cgi?id=163029
So I turn off all encryption methods, and a) I get a warning saying that things won't work. I'm allowed to connect to the url above, I just get certificate warnings. Not that I'm unencrypted. That seems kind of bad. Someone else?
KDE 3 is no longer maintained and since KDE 4 SSL handling is quite different, feel free to reopen this ticket if you have the same issue there.