It makes no sense. I am looking at the -v output.Globalscape seems to think it is the way curl sends the data. Anyway, I have attached my output from -v. If you see any interesting you can share it would help us a lot.

* About to connect() to serv1 port 990
* Connected to serv1 (x.x.x.x) port 990
* successfully set certificate verify locations:
* CAfile: C:\curl\curl-ca-bundle.crt
  CApath: none
* SSL connection using AES256-SHA
* Server certificate:
* subject: /C=US/CN=sl2webserv1/L=webo/OU=remote/O=remote/ST=mass/emailAd
dress=
* start date: 2004-06-09 13:27:41 GMT
* expire date: 2005-06-09 13:27:41 GMT
* common name: serv1 (matched)
* issuer: /C=US/CN=serv1/L=webo/OU=remote/O=remote/ST=mass/emailAdd
ress=
* SSL certificate verify ok.
< 220 GlobalSCAPE Secure FTP Server (v. 2.0)
> USER onalert
< 331 Password required for onalert.
> PASS EMCCONNECT
< 230 Login OK. Proceed.
* We have successfully logged in
> PBSZ 0
< 200 PBSZ Command OK. Protection buffer size set to 0.
> PWD
< 257 "/" is current folder.
* Entry path is '/'
> EPSV
< 500 'EPSV': command not understood.
> PASV
< 227 Entering Passive Mode (10,15,54,102,6,209).
* About to connect() to serv1 port 1745
* Connecting to sl2webserv1 (10.15.54.102) port 1745
* Connected the data stream with PASV!
> TYPE A
< 200 Type set to A.
> LIST
< 150 Opening ASCII mode data connection for file list.
* Doing the SSL/TLS handshake on the data stream
* successfully set certificate verify locations:
* CAfile: C:\curl\curl-ca-bundle.crt
  CApath: none
* SSL re-using session ID
* SSL connection using AES256-SHA
* Server certificate:
* subject: /C=US/CN=serv1/L=webo/OU=remote/O=remote/ST=mass/emailAd
dress=
* start date: 2004-06-09 13:27:41 GMT
* expire date: 2005-06-09 13:27:41 GMT
* common name: slserv1 (matched)
* issuer: /C=US/CN=serv1/L=webo/OU=remote/O=remote/ST=mass/emailAdd
ress=
* SSL certificate verify ok.
* Getting file with size: -1
-rw-rw-rw- 1 user group 24124891 Jun 30 11:49 appmonitor.exe
-rw-rw-rw- 1 user group 358 Jun 30 07:40 test.txt
-rw-rw-rw- 1 user group 1769472 Jun 30 13:34 w_vt_p_7.1.018.exe
< 226 Transfer complete. 282 bytes transferred. 282 bps.
* Connection #0 left intact
> QUIT
< 221 Service closing control connection.
* Closing connection #0

> From: Daniel Stenberg <daniel-curl_at_haxx.se>
> Date: 2004/07/01 Thu PM 06:38:30 GMT
> To: curl tool talk <curl-users_at_cool.haxx.se>
> Subject: Re: Curl & Cute FTP Phenomenon
>
> On Thu, 1 Jul 2004 jennyvus_at_charter.net wrote:
>
> > In the Cute FTP server, there is the settings page which I specifiy to use
> > Implicit FTPs and Require client certificates. When I only specify the
> > following,
> >
> > C:\curl>curl ftps://username:password_at_serv1:990
>
> That's using explicit. Implicit is when you use a ftp:// URL and the --ftp-ssl
> option.
>
> > it still connects, transfers files etc! It should be rejecting me. What is
> > it that is making the connection work?
>
> Use -v and it'll tell you everything it does.
>
> > I have e-mailed Globalscape and they are telling me it is in the curl..
>
> If you've told the server to require a client certificate and it lets you
> through anyway, I fail to see how this is the client's fault.
>
> --
> Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
> Dedicated custom curl help for hire: http://haxx.se/curl.html
>
Received on 2004-07-01