On Tue, 2 Dec 2003, Gisle Vanem wrote:

> It works with "AUTH SSL" as the first command and everything else past that
> is crypt'd. I have only a snippet of the control-connection (at port 21).
> Assume the data-port is 20. AFAICS, curl does the AUTH differently. Brief
> from Ethereal of connection that works:
>
> S->C: FTP Response: 220 godzilla FTP server (Versi .. <pcap truncated>
> C->S: FTP Request: AUTH SSL
> S->C: FTP Response: 334 AUTH SSL OK.
>
> The server (S) is a NetBSD with ftpd-ssl and openssl 0.9.7. So he tells me.

curl issues a 'AUTH TSL' command (lib/ftp.c:487) and expects a 234 response
for success. I guess we should try a 'AUTH SSL' with a 334 response as a
backup plan if the TSL version fails. Can you see if that makes any
difference?

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
 [[ Do not post private mails to this email address. They won't reach me. ]]
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/