[plug] Re: restricting user access

[Jon Miller]

No it'll have to be chroot, because we do not want the user to be able to see any other file other than whats in their home directory.  They are not allowed to cd to any other location.

I'll have a read on chroot.

Thanks



>>> danielax at gmail.com 5:20:40 pm 4/05/2005 >>>
Restrict in what way?
If you want to prevent users from modifying[1] any files that are not
in their home directory, or reading others files, then you need to set
restrictive permissions - for example, the users' home directories
should probably have 700 (or rwx------)  as their permissions, and
permissions elsewhere should be locked down.

If you want to prevent users from even seeing anything else: if you
want them to think that they are at ther root of the filesystem, you
might want to look into chroot. Unfortunatly, this can get
complicated, as they then need, for example, their own shell if they
are going to log in interactively.

If I've misunderstood you, please let me know.

HTH,
Daniel

[1] Users still need to be able to access /usr, for example, as they
need shells/programs/etc.


On 5/4/05, Jon  Miller <jlmiller at mmtnetworks.com.au> wrote:
> Like to know how to restrict a users access to just the directory they are
> assigned to.  This is on a Debian server.
> 
> 
> Thanks
> 
> _______________________________________________
> PLUG discussion list: plug at plug.org.au
> http://www.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
> 

-- 
Neuronstorm: neuronstorm.sourceforge.net
The Neuronstorm Blog: leinad-golb.blogspot.com
_______________________________________________
PLUG discussion list: plug at plug.org.au
http://www.plug.org.au/mailman/listinfo/plug
Committee e-mail: committee at plug.linux.org.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plug.org.au/pipermail/plug/attachments/20050504/e91f6912/attachment.htm>