home *** CD-ROM | disk | FTP | other *** search
- Path: saluki-news.wham.siu.edu!slip106.termserv.siu.edu
- From: jimd@slip106.termserv.siu.edu (Jim Dutton)
- Newsgroups: comp.unix.amiga
- Subject: Solved - Re: Restricted Shells ?
- Date: Mon, 19 Feb 1996 01:31:45 CST
- Organization: Southern Illinois University
- Sender: NNTP@slip106.termserv.siu.edu
- Message-ID: <221b93fc.bb2da@slip106.termserv.siu.edu>
- Reply-To: jimd@slip106.termserv.siu.edu
- NNTP-Posting-Host: slip106.termserv.siu.edu
- Comment: AmigaNOS v2.9p
- In-Reply-To: <4et6ev$l67@rrzs3.uni-regensburg.de>
- (from feyrer@rfhs1012.fh.uni-regensburg.de (Hubert Feyrer))
- (at 2 Feb 1996 14:18:07 GMT)
- X-Mailer: //\\miga Electronic Mail (AmiElm 6.24)
-
- Hi Hubert, on Feb 2 you wrote:
-
- > Jim Dutton (jimd@slip106.termserv.siu.edu) wrote:
- > > Does anyone know of where any of the restricted shells can be found ?
- >
- > I *think* bash can be convinced to act as an restricted shell by calling
- > it rbash or so, please consult the documentation.
-
- It turns out the pdKSH (and many other shell programs) can be copied and
- renamed to r*sh and the shell program will recognize itself as being
- 'restricted', similar to your suggestion.
-
- One could also use the "<shell name> -r" option, or possibly the "set -r"
- command to turn an (inter)active shell into a restricted shell. What I wanted,
- however, was a restricted shell for a special guest login that would be
- adequately limited in its abilities.
-
- By copying pdKSH as rksh, adding this to the /etc/shells file, it was then
- simple to set up a restricted login where the user can't "go anywhere" (I
- set the directory in .profile), but could still "connect to me".
-
-