Date: Sat, 19 Feb 2000 18:19:17 +0900 From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp> To: ache@FreeBSD.ORG Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP Message-ID: <20000219181917Q.shin@nd.net.fujitsu.co.jp> In-Reply-To: <20000218152417.A52305@freebsd.org> References: <20000218103132.A74763@freebsd.org> <20000219044734W.shin@nd.net.fujitsu.co.jp> <20000218152417.A52305@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Could you please create the patch which seems to be safely
> > committed? That will be very much help.
>
> Well, I can try but I need to know most shortest and most trivial EPSV
> check sequence from you since can't check it locally and don't know about EPSV.
EPSV is just enhanced version of PASV, and I think it needs to
check same kind of errors. Maybe same check as getreply() in
ftp/ftp.c will be necessary. About the spec, please check RFC2428.
But the problem is that the error message is printed in
getreply() which is called from command(), because the error
message is sent from server.
So following type of check won't work because when returned
from command(), the error message is already printed out...
> Look at util.c setpeer() function lines
>
> if (command("PASSERVE %s", argv[1]) != COMPLETE) { ...
>
> and below
>
> if (command("SYST") == COMPLETE && overbose) { ...
>
> the check must be in this style...
> --
> Andrey A. Chernov
> <ache@nagual.pp.ru>
> http://nagual.pp.ru/~ache/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000219181917Q.shin>