Jochen, mkdir /usr/local/bin/restricted;ln -s <command> /usr/local/bin/restricted/<command>;...
export PATH=/usr/local/bin/restricted;exec rbash ...boom. Now only the commands you want the user to be able to run will be available. Shell scripts, however, continue to work fine, since their `hash bang' doesn't pay attention to the PATH anyway (which I think is more than slightly objectionable, but that's beyond the scope of this email). Regards, Alex. --- PGP/GPG Fingerprint: EFD1 AC6C 7ED5 E453 C367 AC7A B474 16E0 758D 7ED9 -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS/CM>CC/IT d- s:+ a16 C++(++++)>$ UL++++>$ P--- L++>++$ E+ W+(-) N+ o? K? w---() !O !M !V PS+(++)>+ PE-(--) Y+>+ PGP t+>++ !5 X-- R>++ tv(+) b+(++) DI(+) D++ G>+++ e--> h! !r y>+++ ------END GEEK CODE BLOCK------ On Tue, 14 Nov 2000, Jochen Striepe wrote: > Hi, > > On 14 Nov 2000, Pedro Zorzenon Neto <[EMAIL PROTECTED]> wrote: > > > > When the user logs in, rbash is being executed and the restricted login is > > working well. But, if the user executes 'bash', everything becames > > unrestricted. > > > > How can I deny the execution of shells inside rbash? > > How do you expect any shell script to work if you do so? Or did I just > get something wrong? > > > So long, > > Jochen. > > -- > FAQ zur Newsgroup at.linux: > <http://alfie.ist.org/LinuxFAQ/> > >
