[cobalt-users] Re: [Qube2] prodftp 1.2.0 Fix?

[Mike Vanecek <nospam99@xxxxxxxxxxxx>]

The problem reported in the below message is a known bug in 1.2.0 and CVS
fixes have been put together. See

http://www.proftpd.org/proftpd-l-archive/00-08/msg00106.html
http://www.proftpd.org/proftpd-l-archive/00-08/msg00102.html

Would you please put together a pkg containing the appropriate CVS patches
that fix the problem. Both the Port 500 and PASV problem have been fixed.
Either that, or tell me how to incorporate the CVS patches into the Cobalt pkg
install.

Thanks.


On Sun, 22 Oct 2000 21:56:15 -0500, Mike Vanecek <nospam99@xxxxxxxxxxxx>
wrote:

:>I updated my Qube2 with the October patches including All-System 3.0.2-6449
:>(all patches are installed).  Before the patch I could use ftp via the ssh
:>server on the Qube2 with no problems. I used it last night to upload. After
:>the patch installs using the GUI, everything seems to work OK except I no
:>longer can do a secure ftp via the ssh port.
:>
:>My attempts to do so now result in:
:>
:>Messages log:
:>
:>Oct 22 21:34:08 vanecek proftpd[4920]: host.coba.unt.edu
:>(host.coba.unt.edu[129.120.xx.xxx]) - run-time scoreboard file
:>'/var/run/proftpd/proftpd-inetd' appears to be from a newer version of proftpd
:>(1.2.0).
:>
:>Oct 22 21:34:09 vanecek proftpd[4920]: host.coba.unt.edu
:>(host.coba.unt.edu[129.120.xx.xxx]) - Refused PORT 127,0,0,1,7,195 (address
:>mismatch). 
:>
:>
:>FTP Client:
:>
:>WINSOCK.DLL: WinSock 2.0
:>WS_FTP LE 5.08 2000.01.13, Copyright © 1992-2000 Ipswitch, Inc.
:>local chdir to c:\temp
:>- -
:>connecting to 127.0.0.1:8082
:>Connected to 127.0.0.1 port 8082
:>[144] from 127.0.0.1 port 1986
:>220 ProFTPD 1.2.0 Server (ProFTPD) [host.coba.unt.edu]
:>USER vanecek
:>331 Password required for vanecek.
:>PASS (hidden)
:>230 User vanecek logged in.
:>PWD
:>257 "/users/vanecek" is current directory.
:>SYST
:>215 UNIX Type: L8
:>Host type (S): UNIX (standard)
:>PORT 127,0,0,1,7,195
:>500 Illegal PORT command.
:>! Failed "port":
:>! Retrieve of folder listing failed (0)
:>
:>I have tried both passive and active connections. Different error, but same
:>result. Looks like the patch was too successful.
:>
:>What can I do to get back my ability to use the ssh port for ftp transfers
:>(ssh telnet and web admin work OK, so port forwarding is working)?
:>
:>Can prodftp be configured to ignore the port address mismatch??
:>