curl-users
Re: connects but then nothing
Date: Fri, 6 Oct 2006 11:07:40 -0700
On Fri, Oct 06, 2006 at 01:55:03PM -0400, Dorr, Brad wrote:
> Sorry forgot the ssl. Here are the results. There are 2 tries below on port 21. And 2 on port 990.
>
> curl --ftp-ssl -Svu ????:?? ftp://ftp.initiatesystems.com
> * About to connect() to ftp.initiatesystems.com port 21
> * Trying 66.105.34.179... connected
> * Connected to ftp.initiatesystems.com (66.105.34.179) port 21
> < 220 Initiate Systems Inc. Secure FTP Server (v. 2.0)
> > AUTH SSL
> < 234 AUTH Command OK. Initializing SSL connection.
> * found 60 certificates in /opt/TWWfsw/curl715/share/ca-bundle.crt
> * server certificate verification failed. CAfile: /opt/TWWfsw/curl715/share/ca-bundle.crt
> * Closing connection #0
This is looking good. If you add -k to the command line, you'll probably find
that it works. -k disables certificate checking, so the better solution
is to find what CA was used to sign the server's certificate and add it to
your CA bundle.
> curl -ftp-ssl -Svu ????:????? ftp://www.initiatesystems.com
You're missing a - in --ftp-ssl.
> * About to connect() to www.initiatesystems.com port 21
> * Trying 69.36.45.23... connected
> * Connected to www.initiatesystems.com (69.36.45.23) port 21
> < 220 propel Microsoft FTP Service (Version 5.0).
> > USER ??????
> < 331 Password required for mcla.
> > PASS ?????
> < 530 User ???? cannot log in.
> * Access denied: 530
> * Closing connection #0
> curl -ftp-ssl -Svu ?:?? ftp://www.initiatesystems.com:990
Same thing--missing -
> * About to connect() to www.initiatesystems.com port 990
> * Trying 69.36.45.23... A remote host refused an attempted connect operation.
Looks like the remote server doesn't support any service on port 990. This
host isn't likely to be useful to you.
> * couldn't connect to host
> * Closing connection #0
>
> curl --ftp-ssl -Svu ??:??? ftp://ftp.initiatesystems.com:990
> * About to connect() to ftp.initiatesystems.com port 990
> * Trying 66.105.34.179... connected
> * Connected to ftp.initiatesystems.com (66.105.34.179) port 990
If it's listening on port 990, it's going to be listening for ftps. Change
the URL to ftps://... and you'll see something different.
Of these attempts, the first and last are most likely to do what you want,
but the first (--ftp-ssl) is the more "standard" solution.
>>> Dan
-- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has movedReceived on 2006-10-06