On Tue, Mar 01, 2011 at 08:08:39PM -0500, kalin m wrote:
> On 3/1/11 4:49 PM, Dan Fandrich wrote:
> > 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.
>
> that's not really what happens. even with --ftp-ssl it tries port 21 and eventually times out.

If you'd like advice, you'll have to supply more information. A debug log
is a minimum.

> >> 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?
>
> yes.
>
> > If it works from there, it should work
> > the same way from other machines.
>
> right.
>
> >> .....
> >> 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.
> so in short - after some pain i did get this resolved. i'd think that all this should have been resolved in the last 3 and a half years but i guess it's not a priority.

Did you follow the advice in that bug entry? Did you report a problem to
the OpenSSL developers? I'm not aware of any outstanding problem in the
curl build tools in this area.

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