Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Chris Evans (chrisscary.beasts.org)
Date: Thu Mar 08 2001 - 18:42:40 CST
On Thu, 8 Mar 2001, Alan Cox wrote:
> > I'll be keeping to vsftpd. If I change the name, I'll just confuse myself
> > ;-) Besides, it's almost finished.
> It needs one thing for real world usability - bandwidth control. Its looking
> very nice indeed. May be time to wheel it out on ftp.linux.org.uk before you
> next break all the other ftp daemons
Ouch. I wasn't aware it was a big requirement, I'll add it to the TODO.
Doesn't this sort of policy belong outside an ftpd, though? vsftpd can now
run with all PORT connections coming from port 20 and all PASV connections
being restricted to an admin settable port range. That should be
sufficient to use Linux kernel firewall + QoS to set limits.
I don't want to reinvent the wheel inside vsftpd. I've already been
bouncing lots of requests (connection limits, virtual hosting) with
"xinetd already does that well"