Recently I was asked to create something to grab files from a company's
server with sensitive data in it and the company only supports FTP/S for
this. This lead me to cURL. After building it I did some testing and
was able to transfer files with FTP, SFTP, SCP and so forth. So far I
have had no luck in making a successful connection to grab this file
via FTP/S, though. At first testing he was telling me I need to make an
explicit TLS type of connection. After finding what I thought I needed
to do that, now cURL crashes with a core dump. Unfortunately, I have
no idea if I am supplying the right switches to accomplish what I need.

Is there anyone out there that has a bit of experience with cURL for
doing FTP/S type of transfers?

curl --version
curl 7.18.0 (powerpc-ibm-aix5.3.0.0) libcurl/7.18.0 GnuTLS/1.3.4
zlib/1.2.3 libidn/1.5 libssh2/0.18
Protocols: tftp ftp telnet dict http file https ftps scp sftp
Features: IDN IPv6 Largefile SSL libz

I have tried the following:

curl -v -S --tlsv1 --ftp-ssl --ftp-ssl-reqd -u username:password
--list-only --no-sessionid ftp://server-ip-address:1586/filename.txt

I'm not sure if I need no-sessionid or not, but I thought it couldn't
hurt.

I get the following back in messages:

* About to connect() to IP-address port 1586 (#0)
* Trying IP-address... connected
* Connected to IP-address (IP-address) port 1586 (#0)
< 220-FileZilla Server version 0.9.19 beta
< 220 Welcome to Pearce & Pearce S-FTP
> AUTH SSL
< 234 Using authentication type SSL
Segmentation fault(coredump)

And their logs from this connection show:

(000010) 3/20/2008 16:12:24 PM - (not logged in) (my-IP)> Connected,
sending welcome message...
(000010) 3/20/2008 16:12:24 PM - (not logged in) (my-IP)> 220-FileZilla
Server version 0.9.19 beta
(000010) 3/20/2008 16:12:24 PM - (not logged in) (my-IP)> 220 Welcome to
Pearce & Pearce S-FTP
(000010) 3/20/2008 16:12:24 PM - (not logged in) (my-IP)> AUTH SSL
(000010) 3/20/2008 16:12:24 PM - (not logged in) (my-IP)> 234 Using
authentication type SSL
(000010) 3/20/2008 16:12:24 PM - (not logged in) (my-IP)> disconnected.

Any help or light you can shed on this would be greatly appreciated.
Thanks in advance!

John Heiden
The University of Toledo
Received on 2008-03-20