Restricted (or Captive) Account/Shell

Restricted (or Captive) Account/Shell

Post by Mark Eva » Fri, 27 May 1994 18:52:18



I am looking for a restricted shell (rsh is not secure enough: crtl-Z!)
or captive account mechanism that will restrict what users can do.
Also to log the commands that have been executed. Has anyone written
or knows if such a thing is avaliable ?

Operating Systems: SysVR4 and SunOS4.1.x

Thank you in advance for suggestions.

Regards,

Mark

 
 
 

Restricted (or Captive) Account/Shell

Post by R. Stewart Ell » Fri, 27 May 1994 20:45:25


 >I am looking for a restricted shell (rsh is not secure enough: crtl-Z!)

What will ^Z get them?  if /usr/lib/rsh is their login shell, then they
should only get another rsh.  If you are running a shell script simply trap
all the signals to print a message and exit.

 >or captive account mechanism that will restrict what users can do.
 >Also to log the commands that have been executed. Has anyone written
 >or knows if such a thing is avaliable ?

 >Operating Systems: SysVR4 and SunOS4.1.x

 >Thank you in advance for suggestions.

 >Regards,

 >Mark

--
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______

  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /

 
 
 

Restricted (or Captive) Account/Shell

Post by Dorian Dea » Fri, 27 May 1994 23:44:41



> I am looking for a restricted shell (rsh is not secure enough: crtl-Z!)
> or captive account mechanism that will restrict what users can do.
> Also to log the commands that have been executed. Has anyone written
> or knows if such a thing is avaliable ?

Call it my Incompleteness Theorem:

Any shell powerful enough to be called a shell cannot be restricted.

I suspect people might argue that you can do a chroot, restrict access
to the compiler, etc., but I really think that by the time you've
covered all the holes, you won't have a shell worthy of the name.

(I know this is not a rigorous definition:  you'd have to somehow
precisely define a shell first and be able to determine when a shell
is so restricted it is no longer a shell).

Simple programs with very limited function can be restricted, as long
as they don't, in turn, call something more complex.

dorian

--

House Information Systems
Washington, DC  20515

 
 
 

Restricted (or Captive) Account/Shell

Post by JULIAN PAUL ASSAN » Sat, 28 May 1994 21:59:22




>> I am looking for a restricted shell (rsh is not secure enough: crtl-Z!)
>> or captive account mechanism that will restrict what users can do.
>> Also to log the commands that have been executed. Has anyone written
>> or knows if such a thing is avaliable ?

For an example of a chrooted semi-restricted shell, telnet to
suburbia.apana.org.au and login as "xfer".

- Proff

 
 
 

1. Restricted Shell Account

Anyone out there know anything about setting up user accounts with
restricted shells? I know you have to create or modify the account to use
/usr/lib/rsh as the shell. Where I get hazy is setting up the /usr/rbin
directory. The only references I can find say to create the directory, then
copy or link the commands to it that you want to restrict the user to. OK,
this is a dumb question, but how do you do that? I know how to copy and
link files to a directory, but commands? I just don't quite get it. Any
help would be GREATLY appreciated.

Thanks,
        John

2. Docs about sound programming in Linux ?

3. Temporary restricted shell accounts: howto

4. Trouble with RedHat kernel compilations

5. HELP: DAT should be useable by specific account (restricted shell, etc)

6. XF86Config file for ATI Xpert 2000 (works perfectly) - for those who requested it.

7. Restricted Bash Shell Accounts

8. Connecting to a SLIP server (newbie)

9. Alternative editors to vi (for restricted shell accounts)

10. restricting users with shell accounts

11. Best way for a restricted shell account

12. Captive account

13. Captive Accounts