https://bugs.kde.org/show_bug.cgi?id=322383
Christian Mollekopf <mollek...@kolabsys.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |CONFIRMED CC| |mollek...@kolabsys.com Ever confirmed|0 |1 --- Comment #2 from Christian Mollekopf <mollek...@kolabsys.com> --- The problem is that we're trying to connect using QSsl::AnyProtocol, which suggests it should be able to connect to sslv3 only server, but actually can't. The internally used q_SSLv23_client_method (openssl), sends out a SSLv2 client hello message, but will also indicate that it understands sslv3, so the server could upgrade. However, that doesn't seem to work with sslv3 only servers. So I think we need to add an explicit sslv3 option, or disable sslv2 right away (AFAIK it's not recommended anyways and sslv3 should be widely supported). Regarding the error message, I checked that the error is detected internally, so the resource should enter the broken state. See also: https://groups.google.com/forum/#!msg/phantomjs/QgwweHYv4HU/odbQxCibzDsJ -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs