tar@math.ksu.edu (Tim Ramsey) (06/06/91)
About a week ago someone uploaded 9 or 10 X rated GIFs to my anonymous FTP world-writable incoming directory. Then someone told their friends, and word spread, until my poor machine died due to the number of incoming FTP sessions, all downloading the GIFs. To prevent this sort of problem I need a FTP server that gives me finer control over how many guests can connect at one time, what times they can connect, and that logs everything they do. Here's what I think should be in the ultimate spiffy FTP server: 1) It should provide host based access control, allowing you to disallow access to the server from a host or a domain. In addition, it should allow certain hosts or domains access to directories that the rest of the world can not access. 2) It should log everything done during an anonymous FTP session. 3) It should allow you to limit anonymous FTP access to certain times, and kick people off if they are connected and then enter a "no anonymous FTP" time. 4) Bonus points if it includes a built in "ls" command so you don't have to have /bin, /lib, /dev, /etc, ... Comments? Am I missing anything that the ultimate spiffy FTP server should have? Are there any freely redistributable implementations that do some or all of this? -- Tim Ramsey/system administrator/tar@math.ksu.edu/(913) 532-6750/2-7004 (FAX) Department of Mathematics, Kansas State University, Manhattan KS 66506-2602 "Yes, you can take an axe to the 3084..." -- bav@ksuvm.ksu.edu, realizing the futility of CP/CMS