Steve,
My understanding is that you can't do this in a practical manner. If each
user has a shell account and logs in via ssh, telnet, rlogin, then to
chroot them into their directory you have to place into each directory any
system commands that you want to allow them to run - they're refused
a
At 03:50 PM 10/4/00 , Alan Mead wrote:
>At 11:09 AM 10/4/00 , Steve Curry wrote:
>>/home/username and I don't want them to be able to view any directory
>>structures below their home directory. How do I do this? For example a user
>>called ted in /home/ted shouldn't be able to 'cd' down to /home a
On Wed, 04 Oct 2000 16:50 Alan Mead wrote:
>Also IIRC, in order to allow personal web access (i.e.,
>http://www.ipat.com/~amead serving from
>www.ipat.com:/home/amead/public_html) the users have to give at least read
>permission to everyone for the home and public_html directories.
At least ex
First of all CD'ing from /hom/ted into /home would be cd'ing up, not down
;-)
Anyway, look into what's called "jailing": when user is jailed, it appears to them as
though no other directories exist except their /home/them. if they do "pwd" they'll
see "/" instead of /home/ted, and if they d
At 11:09 AM 10/4/00 , Steve Curry wrote:
>First of all thanks ahead of time! I'm building a multiuser system that will
>be home to many untrusted user accounts. They are being setup in
Unsolicited advice: IMHO it's really hard to keep a system secure if you
cannot trust the users. The vast major
-Original Message-
From: Steve Curry <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, October 04, 2000 2:00 PM
Subject: Locking down a multiuser system.
>List,
>
>
>First of all thanks ahead of time! I'm building a multiuser
List,
First of all thanks ahead of time! I'm building a multiuser system that will
be home to many untrusted user accounts. They are being setup in
/home/username and I don't want them to be able to view any directory
structures below their home directory. How do I do this? For example a user
ca
