On Sun, 21 Sep 2003 15:35:01 -0400, Peter Larsen wrote > > What I would like to be able to do is use the anonymous outgoing read and > > incoming write (with reads blocked) approach for non-local users. Hence, I > > would really like to have a "vsftpd.allowed_emails" file that specifies > > accepted passwords. Then I could give out the current password to a large > > block of folks (such as a college class) without having to set up a ton of > > user accounts. Those folks would know the correct password, could download > > from the public outgoing directory, could write to the public incoming > > directory (without being able to see what others have previously > uploaded). I > > could easily change the password as needed. Those not knowing the password > > would be rejected thereby removing the need for a vsftpd.banned_emails > file. > > Why not just set up a real user, and deny anonymous access (which is > what I do). Setup a user per person, so you can trace abuse, or if > you're brave, allow them to share one account. Have it "chroot" to > where the shared resources are, and you should be pretty safe.
I was trying to avoid having to set up a large number of accounts every semester which would have to be removed at the end of the semester. > > Well, I wouldn't use anonymous access, if you only want certain > people to use it - it sounds contradictive to me. Uhm, I wonder if I can set up a single account that has group access to a download folder and a group write only access to an upload folder ... That might do the trick. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
