Strange SSLSocket Errors

[Yves_Pellot]

I use a SSL socket for FTP secure connections. It works with many severs but there are strange errors for some customer ftp servers.

For ConnectionType=SSLSocket.TLSv12

[quote]Socket: Connected event
← 220 ProFTPD 1.3.6rc2 Server (ProFTPD) [80.74.155.70]
→ AUTH TLS
← 234 AUTH TLS successful
Socket: Set Secure=True
Socket: Error 337056010[/quote]

What means error 337056010?! I thought SSLSocket.TLSv12 is backwards compatible to earlier versions, because the documentation says:

A TLS/SSL connection established with this constant may understand the SSLv3, TLSv1, TLSv1.1 and TLSv1.2 protocols. If extensions are required (for example server name) a client will send out TLSv1 client hello messages including extensions and will indicate that it also understands TLSv1.1, TLSv1.2 and permits a fallback to SSLv3. A server will support SSLv3, TLSv1, TLSv1.1 and TLSv1.2 protocols. This is the best choice when compatibility is a concern.

If I set ConnectionType=SSLSocket.TLSv11, everything works without error.

[quote]Socket: Connected event
← 220 ProFTPD 1.3.6rc2 Server (ProFTPD) [80.74.155.70]
→ AUTH TLS
← 234 AUTH TLS successful
Socket: Set Secure=True
Socket: Connected event
→ USER fishbeam
← 331 Password required for fishbeam
→ PASS ****
← 230 User fishbeam logged in
→ PBSZ 0
…
[/quote]

Is this a Xojo related bug? Because here it seams that SSLSocket.TLSv12 is not backwards compatible to SSLSocket.TLSv11.

[John_A_Knight_Jr]

Use ConnectionType=SSLSocket.SSLv23 for best protocol negotiation.
The other options only support the single protocol specified

[Yves_Pellot]

Thank you. ConnectionType=SSLSocket.SSLv23 solved it for me.