Date: Fri, 1 Dec 2000 10:49:06 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: James Wyatt <jwyatt@rwsystems.net> Cc: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de>, freebsd-security@FreeBSD.ORG Subject: Re: which ftpd Message-ID: <14887.58514.983118.454312@nomad.yogotech.com> In-Reply-To: <Pine.BSF.4.10.10012010332310.42770-100000@bsdie.rwsystems.net> References: <200012010823.JAA24840@gilberto.physik.rwth-aachen.de> <Pine.BSF.4.10.10012010332310.42770-100000@bsdie.rwsystems.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I've found the stock FreeBSD FTPd really good. It offers a chrooted > account I've had to take the WUFTPd risk for before on Linux. If you > turn-up the logging you can easily catch things like this. (btw: this > looks like some warez d00dz building a nest. I've had it happen before and > there have been some FTPd holes that required writable anon-ftp to work.) > Using the FTPd xfer log, you can easily audit uploaded files and spot > things like this. You can also have an automatic process watch the log > and move the files to a quarrantine area. Do you have an example setup you could post to the list? One of the issues I'd like to have is an ftpd that allows uploads, but either moves them or changes the permissions on them as soon as the files are uploaded, to avoid having folks abuse the system for warez. This and the ability to chroot ftpd easily would allow me to switch away from my current ftpd daemon. Having this in the archive may help further users as well... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14887.58514.983118.454312>