Bug 142553 - Confusing error if HTTPS encryption method can't be agreed
Summary: Confusing error if HTTPS encryption method can't be agreed
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-05 16:39 UTC by Olivier Vitrat
Modified: 2012-02-02 00:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Vitrat 2007-03-05 16:39:01 UTC
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.
Comment 1 Olivier Vitrat 2007-03-05 16:39:46 UTC
reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374508
Comment 2 Carsten Lohrke 2007-04-12 18:40:51 UTC
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

Comment 3 A. Spehr 2008-07-23 08:44:55 UTC
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? 
Comment 4 Dawit Alemayehu 2012-02-02 00:40:18 UTC
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.