Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/3/85; site ukma.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!cbosgd!ukma!sean
From: sean@ukma.UUCP (Sean Casey)
Newsgroups: net.unix
Subject: Re: inconsistency on read/execute permissions for shell procedures
Message-ID: <1945@ukma.UUCP>
Date: Tue, 9-Jul-85 01:54:02 EDT
Article-I.D.: ukma.1945
Posted: Tue Jul  9 01:54:02 1985
Date-Received: Thu, 11-Jul-85 04:57:57 EDT
References: <761@wanginst.UUCP>
Reply-To: sean@ukma.UUCP (Sean Casey)
Distribution: net
Organization: The White Tower @ The Univ. of KY
Lines: 15


On BSD systems, the kernel can understand that a file is a shell file
and start a shell to interpret it.  It seems that the shell must me able
to read the file to be able to execute it.  I really do not understand why
this is so, since a simple solution would be to have the kernel hand the
shell the file on standard input if --x access is permitted.  The user
would see the execution, but not the source.

This solution seems so simple that I have probably missed a loophole
somewhere.  If not, why don't "they" do it?
-- 

-  Sean Casey				UUCP:	sean@ukma.UUCP   or
-  Department of Mathematics			{cbosgd,anlams,hasmed}!ukma!sean
-  University of Kentucky		ARPA:	ukma!sean@ANL-MCS.ARPA