<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2627" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px">
<DIV>Thanks I would appreciate it.</DIV>
<DIV> </DIV>
<DIV>Jon<BR><BR>>>> something.rotten@gmail.com 7:26:23 pm 4/05/2005
>>><BR>I'll have to check but on Pegasus I believe we chroot into our
home<BR>directories and the same style thing when we vnc or ftp in, ftp
gives<BR>home and vnc gives you a screen as though your logged in to, say,
a<BR>winxp machine (without the security holes)<BR><BR>i can check on it if
you'd like...we may have a few docvs about it too<BR><BR>On 5/4/05, Jon
Miller <jlmiller@mmtnetworks.com.au> wrote:<BR>> 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.<BR>> <BR>> I'll have a read on chroot.<BR>> <BR>>
Thanks<BR>> <BR>> >>> danielax@gmail.com 5:20:40 pm 4/05/2005
>>><BR>> Restrict in what way?<BR>> If you want to prevent users
from modifying[1] any files that are not<BR>> in their home directory, or
reading others files, then you need to set<BR>> restrictive permissions - for
example, the users' home directories<BR>> should probably have 700 (or
rwx------) as their permissions, and<BR>> permissions elsewhere should
be locked down.<BR>> <BR>> If you want to prevent users from even seeing
anything else: if you<BR>> want them to think that they are at ther root of
the filesystem, you<BR>> might want to look into chroot. Unfortunatly, this
can get<BR>> complicated, as they then need, for example, their own shell if
they<BR>> are going to log in interactively.<BR>> <BR>> If I've
misunderstood you, please let me know.<BR>> <BR>> HTH,<BR>>
Daniel<BR>> <BR>> [1] Users still need to be able to access /usr, for
example, as they<BR>> need shells/programs/etc.<BR>> <BR>> On 5/4/05,
Jon Miller <jlmiller@mmtnetworks.com.au> wrote:<BR>> > Like to
know how to restrict a users access to just the directory they are<BR>> >
assigned to. This is on a Debian server.<BR>> ><BR>> ><BR>>
> Thanks<BR>> ><BR>> >
_______________________________________________<BR>> > PLUG discussion
list: plug@plug.org.au<BR>> > <A
href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</A><BR>>
> Committee e-mail: committee@plug.linux.org.au<BR>> ><BR>> <BR>>
--<BR>> Neuronstorm: neuronstorm.sourceforge.net<BR>> The Neuronstorm
Blog: leinad-golb.blogspot.com<BR>>
_______________________________________________<BR>> PLUG discussion list:
plug@plug.org.au<BR>> <A
href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</A><BR>>
Committee e-mail: committee@plug.linux.org.au<BR>> <BR>> <BR>>
_______________________________________________<BR>> PLUG discussion list:
plug@plug.org.au<BR>> <A
href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</A><BR>>
Committee e-mail: committee@plug.linux.org.au<BR>> <BR>> <BR>>
<BR>><BR>_______________________________________________<BR>PLUG discussion
list: plug@plug.org.au<BR><A
href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</A><BR>Committee
e-mail: committee@plug.linux.org.au<BR></DIV></BODY></HTML>