home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 October
/
usenetsourcesnewsgroupsinfomagicoctober1994disk2.iso
/
std_unix
/
v22
/
123
< prev
next >
Wrap
Internet Message Format
|
1991-03-07
|
2KB
From jsq@cs.utexas.edu Wed Feb 13 10:41:40 1991
Received: from cs.utexas.edu by uunet.uu.net (5.61/1.14) with SMTP
id AA03237; Wed, 13 Feb 91 10:41:40 -0500
Received: by cs.utexas.edu (5.64/1.94)
From: Chuck.Phillips@FtCollins.NCR.COM (Chuck.Phillips)
Newsgroups: comp.std.unix
Subject: Re: "#!" magic number (was: Shell standardization)
Message-Id: <17838@cs.utexas.edu>
References: <17011@cs.utexas.edu> <17065@cs.utexas.edu> <17155@cs.utexas.edu> <17650@cs.utexas.edu>
Sender: jsq@cs.utexas.edu
Organization: NCR Microelectronics, Ft. Collins, CO
X-Submissions: std-unix@uunet.uu.net
Date: 12 Feb 91 15:03:33 GMT
Reply-To: std-unix@uunet.uu.net
To: std-unix@uunet.uu.net
Submitted-by: Chuck.Phillips@FtCollins.NCR.COM (Chuck.Phillips)
>>>>> On 4 Feb 91 11:50:07 GMT, Chuck.Phillips@FtCollins.NCR.COM (Chuck.Phillips) said:
Chuck> Invitation for discussion: If the path after the "#!" doesn't begin
Chuck> with "/", "./" or "../", should PATH be searched for the execuatble?
Chuck> If so, how best could this be implemented?
Based on feedback from Ernest Hua (thanks!), I'd like to ammend this. SUID
scripts under no circumstances should allow PATH searching for '#!'
arguments -- even if not SUID root.
Continuing the earlier thread, not only are directory structures
non-portable, but some interpreters (e.g. pearl, gawk, bash) have no POSIX
or otherwise defined directory location. '#!' path searching also allows
vendors to write their own interpreters for scripts without forcing a
particular directory structure on admin. Further, it allows different
versions of the same interpreter to be used simultaneously based on each
user's path.
--
Chuck Phillips MS440
NCR Microelectronics chuck.phillips%ftcollins.ncr.com
2001 Danfield Ct.
Ft. Collins, CO. 80525 ...uunet!ncrlnk!ncr-mpd!bach!chuckp
Volume-Number: Volume 22, Number 123