> I want to set up my ftpd daemon (uh, oh, that word "daemon" again
> <grin>) to allow for access to the /pub directory ONLY. I'd like to
> allow both read and write access, but only allow any ftpuser to see
> that directory ONLY (and any subdirectories to it).
Do you mean /pub, or do you mean /home/ftp/pub, which is what an
anonymous user sees when he asks for /pub? I can see good reason for
incoming to be write only, and pub read only, to give you (or your
daemons:-) a chance to look it over before you publish it to the world.
It is easy enough to make /home/ftp/pub world writable, but if you want
this to be the same as /pub, the easiest way I can see to do it would be
to move /pub to /home/ftp/pub, and then make /pub a symbolic link to it.
I don't think you can do it the other way round. As to limiting
visibility to just pub, ftpd doesn't trust itself, so it limits itself
when serving an anonymous user, to the fs rooted at /home/ftp. It needs
to be able to see the files in bin and lib to be able to execute
commands.
>
> I've been mucking around with permissions, ftpaccess, etc, but I don't
> seem to be able to hit on the right combo. can somebody point me to a
> FAQ, or give me some advice?
>
>
>
>
> Casey Bralla
> Chief Nerd In Residence
> The NerdWorld Organisation
>
> http://www.NerdWorld.org
> LinuxList@NerdWorld.org
>
Lawson
>< Microsoft free environment
This mail client runs on Wine. Your mileage may vary.
___________________________________________________________________
Get the Internet just the way you want it.
Free software, free e-mail, and free Internet access for a month!
Try Juno Web: http://dl.www.juno.com/dynoget/tagj.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu