On Tue, Mar 01, 2011 at 05:32:55AM -0500, kalin m wrote:
> 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.

Yes, with ftp:// curl tries port 21. But with --ftp-ssl, it will
attempt to switch to SSL after connection. This is the only standards-
compliant method of making an FTP SSL connection.

> 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

Are you saying that curl actually does connect to the desired server
successfully from one machine? If it works from there, it should work
the same way from other machines. If not, then there's a good chance that
there's a firewall in the way of the other clients. Note that only one -v
is necessary.

> 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...

Are you building 7.21.4 or 7.18.2? If there was a build problem in
7.18.2, it may have been fixed since then. Take a look at the config.log file
to get some clues as to why it isn't picking up the new OpenSSL version.

>>> 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
Received on 2011-03-01