(when using OpenSSL).

reacts properly according to the CURLOPT_FTP_SSL setting.

512 bytes could have random garbage appended.  Also, stop processing TFTP
packets which are too short to be legal.

text from OpenSSL.

with the multi interface and multi-part formposts. The fix from February
22nd could make the Curl_done() function get called twice on the same
connection and it was not designed for that and thus tried to call free() on
an already freed memory area!

is used properly.

callback" error message so I've now made the setting of that callback not be
as critical as before. The function is only used for additional loggging/
trace anyway so a failure just means slightly less data. It should still be
able to proceed and connect fine to the server.

accordingly.