Horatio B. Bogbindero writes:
> oops then you are not talking about remote shell(rsh) but restricted bash.
> i am not sure were to get it. but, what i do is get the bash source.
> looking at the main header file you will see a macro called RESTRICT. just
> uncomment it. i did this a looooooooooooong time ago and am not sure if
> the never sources of bash will have this.
>From a running program's perspective, the 'cd' shell command just sets up
an environment for execution (so the OS can tell the shell's child
processes what the current working directory is). Taking out 'cd' from the
shell doesn't really do much, since the user can just call programs using
/full/path/to/progam. What I think you want to do is let users log on in a
chroot jail, and/or be very stingy with file permissions.
But if this is the case, why even have local users on your system at all?
If you don't trust them 100%, don't give them accounts on the machine.
Problem solved.
> On Sat, 26 Aug 2000 [EMAIL PROTECTED] wrote:
> > On Fri, 25 Aug 2000 [EMAIL PROTECTED] wrote:
> > > [brianb@brianb brianb]$ rpm -qf /usr/bin/rsh
> > > rsh-0.10-28
> > >
> > > Install the rsh-0.10-28 rpm. I don't know why you'd want to use rsh instead
> > > of ssh.
> >
> > Because I want to restrict some commands use by users.
> > Just like "cd".
--
Brian Baquiran <[EMAIL PROTECTED]>
http://www.baquiran.com/ AIM: bbaquiran
Work: +63(2)7182222 Home: +63(2) 9227123
I'm smarter than average. Therefore, average, to me, seems kind of stupid.
People weren't purposely being stupid. It just came naturally.
-- Bruce "Tog" Toganazzini
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
