Click to See Complete Forum and Search --> : stopping users having access to the file tree


wendo
11-13-2001, 08:30 AM
i would like to give out shell accounts to people but i cannot stop them being able to cd ../ all the way up the file tree.They can not remove or damage anything but i want to make thier home directory thier root so they cannot go up any further.
Any suggestions?

Kind Regards :D

wendo
11-13-2001, 11:19 AM
come on wake please :) :D :D :D

ph34r
11-13-2001, 11:38 AM
Sounds like you want a chroot environment. I've not set one up, but there should be plenty of docs on it. Start with "man chroot".

wendo
11-13-2001, 03:44 PM
thxs for the chroot command that is not really what i want to do.
i need to change permissions of file types and directories,
but i need an easy way to do it is there such a way?

bdg1983
11-13-2001, 04:56 PM
Originally posted by wendo:
<STRONG>come on wake please :) :D :D :D</STRONG>

I was awake at that time, but at work. And the company doesn't pay my salary to spend time at Linuxnewbie. Sorry about that.

Choozo
11-13-2001, 05:02 PM
Making sure that your 'shell account users' belong to a group that have no access/read permissions outside their own home dir would probably solve it?

Cheers :)

reideemed
11-14-2001, 08:21 PM
this message is just to get the post on the front page again :)

Urko
11-14-2001, 08:41 PM
You want a restricted shell

man rbash

wendo
11-15-2001, 08:49 AM
no manual entry for rbash. :)im using mandrake 8

demetrius
11-15-2001, 12:12 PM
The man page is the same as for bash. Look in the bash man page for the -r or --restricted switches.
A restricted shell or a chroot jail is, I believe, the only way to accomplish what you want to do. If you start restricting read or execute access (and even write access to some directries) your users will be logging in to a useless evironment. Everyone needs access to folders like /usr/bin and everyone needs access to /tmp for example. If you restrict access to these sorts of directories there will be little point in allowing users into the system in the first place.

wendo
11-15-2001, 01:11 PM
DemEtri can you exspand on what you said?

Jomboni
11-15-2001, 05:41 PM
Originally posted by Logon Name Gone:
<STRONG>I was awake at that time, but at work. And the company doesn't pay my salary to spend time at Linuxnewbie. Sorry about that.</STRONG>
Really? You should talk to your boss about that! :D

Dark Ninja
11-15-2001, 06:01 PM
DemEtri can you exspand on what you said?

Basically what he is saying is this -- if you close down your entire system to users, and they aren't able to access ANYTHING, there's no point in allowing users to log into your system. Think about it. Do you want to be the user of a system that doesn't allow you to do anything but sit in your home directory and look at a blank black screen with a little command prompt. No. So, you have to allow them to have access to certain places (like /usr/bin) which will give them a reason to be on your system.

...actually...I was just thinking. What you are trying to do reminds me of those stupid *** "free shells" that I used to use to try to learn a *nix system when I first began using computers. They sucked very bad. Please don't do that to your users. :rolleyes:


Dark Ninja

[ 15 November 2001: Message edited by: Dark Ninja ]

wendo
11-15-2001, 07:18 PM
i only want them to run bots and things from the account :)