Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!pacbell!att!ttrdc!levy
From: levy@ttrdc.UUCP (Daniel R. Levy)
Newsgroups: comp.sources.d
Subject: Re: Poll on shar formats
Message-ID: <2738@ttrdc.UUCP>
Date: 8 Jun 88 00:20:21 GMT
References: <889@fig.bbn.com>
Organization: AT&T, Skokie, IL
Lines: 15

In article <889@fig.bbn.com>, rsalz@bbn.com (Rich Salz) writes:
# For what my opinion is worth, based on the stuff I've read here and gotten
# through the mail, I think there are only two ways to handle leading X's
# (or whatever) on shar scripts:
# 	either Always do it
# 	or Never do it
# Protecting only "dangerous" characters:
# 	Makes it hard to do "grep -v '^X'" to find trojan horses

That's not foolproof.  Someone could package a trojan horse in an apparently
X-protected shell script very easily.  Use your imagination.
-- 
|------------Dan Levy------------|  THE OPINIONS EXPRESSED HEREIN ARE MINE ONLY
|    AT&T  Data Systems Group    |  Weinberg's Principle:  An expert is a
|        Skokie, Illinois        |  person who avoids the small errors while
|-----Path:  att!ttbcad!levy-----|  sweeping on to the grand fallacy.