https://bugs.kde.org/show_bug.cgi?id=394770
--- Comment #3 from Juri Vitali <j...@dbzero.it> --- Poking around the code a bit more, I think a sane default would be to use KTcpSocket::SecureProtocols, which is equal to QSsl::SecureProtocols, which in turn is defined to be by the official docs "The default option, using protocols known to be secure; currently behaves similar to TlsV1Ssl3 except denying SSLv3 connections that does not upgrade to TLS." [1]. Other than that, a switch could be given to the user to use a specific - more secure - protocol, but beyond that an update to KIO would be required, as KTcpSocket seems to be supporting only a limited subset of the Qt's TLS protocols. [2] [1]: https://doc.qt.io/qt-5/qssl.html#SslProtocol-enum [2]: https://api.kde.org/frameworks/kio/html/ktcpsocket_8h_source.html -- You are receiving this mail because: You are watching all bug changes.