Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC840302); site boring.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!mcvax!boring!guido
From: guido@boring.UUCP
Newsgroups: net.unix
Subject: Re: inconsistency on read/execute permissions for shell procedures
Message-ID: <6503@boring.UUCP>
Date: Thu, 11-Jul-85 16:09:22 EDT
Article-I.D.: boring.6503
Posted: Thu Jul 11 16:09:22 1985
Date-Received: Sat, 13-Jul-85 10:18:34 EDT
References: <761@wanginst.UUCP> <1945@ukma.UUCP>
Reply-To: guido@mcvax.UUCP (Guido van Rossum)
Distribution: net
Organization: "Stamp Out BASIC" Committee, CWI, Amsterdam
Lines: 16
Apparently-To: rnews@mcvax.LOCAL

In article <1945@ukma.UUCP> sean@ukma.UUCP (Sean Casey) writes:
>
>        ... since a simple solution would be to have the kernel hand the
>shell the file on standard input if --x access is permitted.  ...
>
>This solution seems so simple that I have probably missed a loophole
>somewhere.  If not, why don't "they" do it?

Simple: the shell's standard input is also the shell file's standard input,
and with your proposed solution the shell script wouldn't be able to read
interesting user data from its standard input, wouldn't be usable as a filter,
etc.  So the contents of the shell file has to be presented to the shell
without closing or dupping the standard input.

	Guido van Rossum, CWI, Amsterdam
	guido@mcvax.UUCP