...due to the newly added CURL_SSLVERSION_MAX_* functionality

synced with df665f4df0f7a352

If the NSS code was in the middle of a non-blocking handshake and it
was asked to finish the handshake in blocking mode, it unexpectedly
continued in the non-blocking mode, which caused a FTPS connection
over CONNECT to fail with "(81) Socket not ready for send/recv".

Bug: https://bugzilla.redhat.com/1420327

Fully implemented with the NSS backend only for now.

Reviewed-by: Ray Satiro

Fully implemented with the NSS backend only for now.

Reviewed-by: Ray Satiro

... but make sure we use at least TLSv1.0 according to libcurl API

Reported-by: Cure53
Reviewed-by: Ray Satiro

... in case the handshake completes before entering
CURLM_STATE_PROTOCONNECT

Bug: https://bugzilla.redhat.com/1388162