>On Thu, Mar 20, 2008 at 04:38:52PM -0400, Heiden, John wrote:
>> 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
>
> What is FTP/S? Are you talking about FTPS? I'll assume you are.
Yes, same thing. I mentioned FTPS to somebody here, and they said I
must
mean SFTP. I told them no, not the same. So they then said I should
use
FTP/S, but in any event, same thing. (I have seen it written somewhere
as
FTP/SSL as well.)

>> 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
>
> That shows ftps support, so you're good there.

I was kind of hoping so. =-)

>> 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
>
>--list-only is only for directories; I'm not sure what it will do when
you
>use it on a file. Otherwise, the command looks fine.
>
>> I'm not sure if I need no-sessionid or not, but I thought it couldn't
>> hurt.
>
>You're right, it shouldn't. But maybe it does--have you tried without?

OK, I tried it again without the --list-only and also without the
--no-session-id
and exact same results:

* 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)

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

>That's a serious problem. You should never, ever get a segfault no
>matter what options you use or what the remove server sends. Can you
run
>this under a debugger and find out where it's dumping core? Noone is
>running an AIX autobuild with SSL support, so it's possible there is a
>latent issue on that platform. Have you tried running the curl test
>suite? There are a number of test cases there that should show a
problem
>if it exists on your platform.

Yeah, I was kind of surprised to get a segfault too. I am willing to
try
anything, but you would need to point me at what you want me to try.
I have never used the debugger on this system before, so not sure what
to
say about that.

Where can I find the "curl test suite"? Point me at what you want and I
am willing to help/provide whatever I can.

>> 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.
>
>That matches well the log above.

Yeah, I kind of thought the same.

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