hey Dan...

thanks for the reply...

no matter what flags i add to the command it always hangs on:

 * SSLv3, TLS handshake, Client hello (1):
} [data not shown]

curl: (35) Unknown SSL protocol error in connection to xx.xx.xx.xx:990

if i just use ftp://.. curl tries port 21. so if i put :990 after the domain i get the same result as the above.
i did use --ftp-ssl-control. same result.

i tried this from 3 different os machines. only one machine works - an os x. with OpenSSL 1.0.0c

this is what works on the os x:

curl --ftp-ssl -vvvv -3 -k 'ftps://user:pass_at_xx.xx.xx.xx/in/' -T test113

the system i need it to work on is:

curl 7.18.2 (x86_64-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 libssh2/0.18
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz

by the way i was trying to reinstall openssl and curl. openssl was installed successfully. when it comes time for curl, running

# ./configure --with-ssl

or

# ./configure --with-ssl=/usr/local/ssl

i get:

.....
configure: WARNING: SSL disabled, you will not be able to use HTTPS, FTPS, NTLM and more.
configure: WARNING: Use --with-ssl, --with-gnutls, --with-polarssl, --with-nss or --with-axtls to address this.
......

  SSL support: no (--with-{ssl,gnutls,nss,polarssl,axtls} )

and did make clean a few time to make sure i was starting from scratch...

the new openssl version is OpenSSL 1.0.0d 8 Feb 2011 but curls configure script is not seeing it...

the current curl is still build with 0.9.8g...

this is getting a bit embarrassing.

thanks...

On 2/28/11 2:06 PM, Dan Fandrich wrote:
> On Fri, Feb 25, 2011 at 07:17:29PM -0500, kalin m wrote:
>> i've been trying to use curl to upload a file to an ftps machine with
>> a filezilla server. and it always hangs at the time of the actual file
>> transfer. i would need some help to figure out why...
>>
>> here is what happens:
>>
>> # curl -vvvv -T test4 --ftp-ssl -d -k -3 --cacert 'tatts.crt' 'ftps://user:pass_at_xx.xx.xx.xx/in/'
>
> Implicit SSL FTP is not well standardized, so it's not surprising you're
> finding issues. Some servers are set up on port 990 with stunnel, so it's
> impossible to encrypt data traffic with those. Those servers do the
> equivalent of --ftp-ssl-control. If you don't need the data traffic
> encrypted, try adding that option. The best route would be to use explicit
> SSL; since you already have the --ftp-ssl option, just change the ftps:// to
> ftp:// and see what happens.
>
>>>> Dan
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-users
> FAQ: http://curl.haxx.se/docs/faq.html
> Etiquette: http://curl.haxx.se/mail/etiquette.html
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-03-01