home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!unixg.ubc.ca!kakwa.ucs.ualberta.ca!access.usask.ca!ccu.umanitoba.ca!mills
- From: mills@ccu.umanitoba.ca (Gary Mills)
- Newsgroups: comp.sys.sun.admin
- Subject: Re: creating restricted shell environments
- Message-ID: <1992Aug15.025535.9527@ccu.umanitoba.ca>
- Date: 15 Aug 92 02:55:35 GMT
- References: <1992Aug6.135112.23720@lokkur.dexter.mi.us> <1992Aug10.171606.11806@oakhill.sps.mot.com> <1992Aug14.201534.1805@ultra.com>
- Organization: University of Manitoba, Winnipeg, Canada
- Lines: 22
-
- In <1992Aug14.201534.1805@ultra.com> rfj@ultra.com (Ray Jackson) writes:
-
- >In <1992Aug10.171606.11806@oakhill.sps.mot.com> guri@sps.mot.com
- >(Gurvinder Singh Ahluwalia) writes:
-
- >>Thanks for the one restriction pointed out. Does someone have a
- >>list of restrictions that are implemented by the Bourne Shell. I
- >>am particularly interested in SunOS 4.1.1.
-
- > I just tried setting up an account under 4.1.2 that runs /usr/lib/rsh.
- >It's not very restricted:
-
- [example omitted]
-
- In the user's .profile or in /etc/profile, you should also restrict PATH
- to a directory that contains only ``safe'' commands. /usr/rbin is a
- suggestion I saw in a sh(1) manual. Vi, csh, ucb/mail, and more are not
- safe because they let you cd, set environment variables, or exec other
- commands. The restrictions, by the way, are only enforced after
- /etc/profile and .profile are interpreted.
- --
- -Gary Mills- -Networking Group- -U of M Computer Services-
-