http://linux.ucla.edu/pipermail/linux/2005-January/009741.html
Mlist: [UCLA-LUG] Date: Jan 4 2005
> Not surprisingly, I can no longer ftp to www.bol.ucla.edu now that > there's SSL/TSL in place. If I do > > $ ftp www.bol.ucla.edu > > ...username and password I get > > 550 SSL/TLS required on the control channel > Login failed. > > and if I try with lftp I get > [Connecting...] > [Receiving data]
try
lftp set ftp:ssl-force true connect www.bol.ucla.edu login <username>
that works with lftp 3.0.11. it should work with releases as early as 2.4.9 (my copy of 2.4.9 isn't linked to openssl so i can't verify, but the man page suggests that it should work).
i've also verified that access works with the standard netkit ftp with the ssl/tls patches applied. check and see if you have ftp-ssl, or if /usr/bin/ftp is linked to libssl.
chris
> I tried what you suggested and it still didn't work. I don't have > ftp-ssl; How can I check if my /usr/bin/ftp is linked to libssl? Thanks > for your help Chris!
ldd /usr/bin/ftp
i would guess that you don't have an ssl-linked ftp client. in my testing, i did have some problems that were cured by forcing the client to use passive mode. that is especially likely to help out if you're trying to ftp from behind a device that is doing nat. you could try
lftp set ftp:passive-mode true set ftp:ssl-force true connect www.bol.ucla.edu login <username>
chris