Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!emory!att!att!fang!tarpit!bilver!bill From: bill@bilver.uucp (Bill Vermillion) Newsgroups: comp.unix.shell Subject: Re: restricted shell sought Message-ID: <1991Apr27.022544.11035@bilver.uucp> Date: 27 Apr 91 02:25:44 GMT References: <29183@fs1.NISC.SRI.COM- <1991Apr25.040344.15655@gpu.utcs.utoronto.ca> Distribution: comp Organization: W. J. Vermillion - Winter Park, FL Lines: 30 In article >>>> On 25 Apr 91 04:03:44 GMT, jmason@gpu.utcs.utoronto.ca (Jamie Mason) said: - -JM> In article <29183@fs1.NISC.SRI.COM> cwilson@NISC.SRI.COM (Chan Wilson [Animal]) writes: -> Basically what i'm looking for is a shell that ->will only allow the user to access a specific subset of commands, and ->not progress upwards beyond a certain point in the directory tree. -JM> Sorry if there was a little too much flame in there. I was -JM> subjected to just such a restricted shell in the past, and it left a -JM> permanent scar. :-) -Well, this is definately sometimes necessary. Take the following example: -We have two full disks containing only data for our lab. We need -to allow read access to this data, but nothing else. We don't have ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -the disk space to simply copy the data over to the ftp files. So, -basically, restricted shells *are* needed for special cases. Maybe -I am forgetting something, but I don't think so. *8-) How about mounting the drives read only. /etc/mount /dev/whatever /wherever -r -- Bill Vermillion - UUCP: uunet!tarpit!bilver!bill : bill@bilver.UUCP