Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watcgl!onfcanim!dave
From: dave@onfcanim.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: \"special\" shells a security hole?
Message-ID: <15222@onfcanim.UUCP>
Date: Thu, 19-Feb-87 11:35:11 EST
Article-I.D.: onfcanim.15222
Posted: Thu Feb 19 11:35:11 1987
Date-Received: Fri, 20-Feb-87 01:35:57 EST
References: <3953@brl-adm.ARPA> <2590002@hpisod2.HP> <3037@gitpyr.gatech.EDU> <177@quacky.mips.UUCP> <1684@druhi.UUCP>
Reply-To: dave@onfcanim.UUCP (Dave Martindale)
Organization: National Film Board / Office national du film, Montreal
Lines: 15

In article <1684@druhi.UUCP> clive@druhi.UUCP (Clive Steward) writes:
>
>    find interestingdir \
>	\( -name Makefile -o -name makefile -o -name \*\.mk \) (etc.) \
>	-exec addshellname {} \;

Unfortunately, it won't find things like "Makefile.v7" and "Makefile.usg"
which are the "master" makefiles for some software.  It also won't
find "makefile.old" or a makefile that is packed into a shar or tar
or compress file.

I'd much prefer to fix make so it behaves in a way that seems reasonable.
Importing SHELL from the environment does not seem reasonable.
(Neither does importing TERMCAP, but at least that doesn't actively
break anything).