Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84 exptools; site ho95e.UUCP Path: utzoo!linus!decvax!tektronix!uw-beaver!cornell!vax135!houxm!ho95e!wcs From: wcs@ho95e.UUCP (x0705) Newsgroups: net.unix Subject: Re: Alternate Shells Message-ID: <162@ho95e.UUCP> Date: Wed, 14-Aug-85 20:09:20 EDT Article-I.D.: ho95e.162 Posted: Wed Aug 14 20:09:20 1985 Date-Received: Tue, 20-Aug-85 08:09:31 EDT References: <10672@Glacier.ARPA> Organization: AT&T Bell Labs, Holmdel NJ Lines: 15 > A quickie: 4.2BSD chsh does not allow the user to specify alternative > shells - only "sh" and "csh" are permitted. Why is this? It seems > ironically inappropriate in UNIX, where the shell is ``an ordinary, .... > Conor Rafferty conor@su-glacier.arpa It's especially annoying if you want ksh. The problem is that chsh is a setuid program that hacks the password file, so it has to be very restricted in its behaviour to avoid being a total security hole. Our local System V Rel 2 systems have a more flexible variant on chsh; I'm not sure if they're part of the vanilla distribution or if they're part of the standard Bell Labs add-on package, but it has a file of legal shells you can use. -- ## Bill Stewart, AT&T Bell Labs, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcs