GitLab

This does not change any of the logic to apply encryption yet, ie. that
is still tied to LoginJob. This however now enables moving that logic
step by step to Session and thus enable encryption independent of a login
being required.

This is a leftover from when this was using KTcpSocket, and nowadays was
merely passing around what is the default anyway.

Test Plan:
Tested TLS and plain connection against my Postfix server and SSL connection
against Gmail.

Reviewers: vkrause

Reviewed By: vkrause

Subscribers: vkrause, kde-pim

Tags: #kde_pim

Maniphest Tasks: T11533

Differential Revision: https://phabricator.kde.org/D23925

Allow only choosing between no encryption, SSL/TLS or STARTTLS and let
KTcpSocket negotiate the best encryption protocol with the server.

FIXED-IN: 5.8.2
BUG: 394770

The protocols are actually different and we only implement XOAUTH2.

Incorrect mapping from KTcpSocket::SslV3_1 caused the LoginJob
to not properly proceed with authentication if TLSv1 was negotiated.

Added NTLM, GSSAPI and Anonymous methods.

Because David said so :)