Bug 116108

Summary: TLS turned on, but can't connect to server
Product: [Frameworks and Libraries] kio Reporter: Thilo Bangert <thilo.bangert>
Component: ksslAssignee: George Staikos <staikos>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Thilo Bangert 2005-11-11 03:31:17 UTC 
Version:            (using KDE KDE 3.4.3)
Installed from:    Gentoo Packages

https://kis.hosteurope.de is the affected site. They apparently only support SSL 2.0 and TLS 1.0...

connecting with firefox - SSL2.0 off, SSL3.0 on, TLS 1.0 on - works

connecting with firefox - SSL2.0 off, SSL3.0 on, TLS 1.0 off - yields in a error 'Can't connect because SSL2.0 is turned off'

in konqueror - SSL2.0 off, SSL3.0 on, 'Use TLS if supported by server' on - yields 'No Connection to host kis.hosteurope.de'

Turning off 'Use TLS if supported by server' doesn't have any effect.

bangert@marsupilami ~ $ openssl version
OpenSSL 0.9.7e 25 Oct 2004
Comment 1 Thiago Macieira 2005-11-11 03:50:22 UTC 
Works fine here, SSLv2 is enabled.
Comment 2 George Staikos 2005-11-11 03:54:35 UTC 
On Thursday 10 November 2005 21:50, Thiago Macieira wrote:
> Works fine here, SSLv2 is enabled.


  Yeah that's what he said... but SSLv2 is insecure and obsolete.  That's why 
it's gone in KDE4.  Apparently there is a compatibility issue here.
Comment 3 Thiago Macieira 2005-11-11 04:00:36 UTC 
Hmm... right, I've reread the report now.

Yes, it makes sense now: if SSLv2 and TLSv1 are off, they won't be used. If that's all the site can talk, you will not be able to connect.

Is the problem the fact that you can't turn TLSv1 on?
Comment 4 Thilo Bangert 2005-11-11 11:55:20 UTC 
Thiago: who is your question directed to?

The problem I am experiencing is, that it doesn't work even though I turned on TLSv1 (I suppose that is what the 'Use TLS if available' checkbox means).
Comment 5 George Staikos 2005-11-13 02:50:05 UTC 

*** This bug has been marked as a duplicate of 108388 ***