>> >How do VirtualHosting services restrict access to ftp only? The
>> >users must still be in the password file right? But how does this
>> >stop users from travessing the directory trees to other places on
>> >the system?
>> >Anyone doing this, or know how its done?
>> It's done very carefully :-)
>> Try man ftpd and look for the word 'chroot'.
>So you mean, that according to this - that EVERY user has their
>own directory tree set up like the anonymous ftp user! etc and bin
>directories, a mini password file etc!
You only need the password file is they need to see the names of
other users. But since they are logged into their own directory they
don't need those. You can then put whatever they need in their own
bin and etc directories. As for the files they would need in their
own bin or etc you could probably put them in one file with links to
the names of the programs as in the /stand directory. . {gawd - I'm
embarrased to say I forgot the name of the program which does this
for the files in the /stand directory}
That way you could just copy one file in to a directory and expand
the links. Anything that goes in their home directory could be
added to /usr/share/skel. I have an index.html along with the
dot.xxxx files to put in a generic holding html for their website
until they bring that up.
Quote:>This
> feature is intended as a compromise between a fully
>anonymous
> account and a fully privileged account. The account should
> also be set up as for an anonymous account.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ????
[woops - deleted the line where you said it was unworkable]
I guess it depends on how much you want to automate and how
far you want to restrict people.
--