lftp-3.0.5 and secure FXP

Hello,

Just tested secure FXP using the new lftp-3.0.5. I
would like to make a suggestion.

As reported in my last post, when sending files from
BlackMoon to my Serv-U 4.x where, Serv-U is behind a
firewall which doesn't allow outgoing traffic to
non-standard ports (but allows incoming traffic to
certain non-standard ports), lftp sends CPSV to Serv-U
then Serv-U says it doesn't know CPSV, then lftp tries
to reverse ftp:fxp-passive-source and sends SSCN ON
followed by PASV to BlackMoon, then Serv-U tries to
connect to BlackMoon but it can't because of the
firewall. My suggestion is lftp should try to reverse
ftp:fxp-passive-sscn first. In my case it would turn
on SSCN on BlackMoon side and still issue PASV on
Serv-U side which would then allow the transfer. In
other cases it should work too and it doesn't take
time to find out (in contrast to reversing
ftp:fxp-passive-source which takes longer time to know
that one server cannot access the other in reverse
direction because, for example, the traffic is blocked
in the middle). If reversing ftp:fxp-passive-sscn
doesn't work, lftp can still try to reverse
ftp:fxp-passive-source next.

A question, as in above case when initiating secure
FXP, lftp issues CPSV on Serv-U side first although
CPSV is not in the FEAT reply. If the server is
changed from Serv-U to Raiden, lftp will issue SSCN ON
instead of CPSV although lftp didn't get a FEAT reply
from Raiden. My question is how doesn't lftp know
whether to issue CPSV in Serv-U case or SSCN in Raiden
case?

Cheers,
Rob.



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/