Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83 based; site homxb.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!homxb!os848
From: os848@homxb.UUCP (M.AJEMIAN)
Newsgroups: net.news.adm,net.news.sa,net.sources.d,net.wanted.sources
Subject: Re: Beware of Blindly Un-SHARing a File
Message-ID: <1449@homxb.UUCP>
Date: Sat, 19-Apr-86 18:10:27 EST
Article-I.D.: homxb.1449
Posted: Sat Apr 19 18:10:27 1986
Date-Received: Mon, 21-Apr-86 01:51:56 EST
References: <947@kitty.UUCP> <2407@prls.UUCP> <1439@garfield.columbia.edu>, <340@imagen.UUCP>
Organization: AT&T Bell Labs, Holmdel NJ
Lines: 23
Xref: watmath net.news.adm:616 net.news.sa:276 net.sources.d:130 net.wanted.sources:2199

About the X that many shars put in the first column...

> Most shar files use the hack of having sed put a 'X' at the beginning
> of every line in the files to be extracted.  This makes it impossible
> for the "termination string" to appear in the file and screw things
> up.  This kind of shar file is easy to check for trojan horses.  Just
> run:
> 	grep '^[^X#]' file.shar
> and grep will print out all the lines of the shar file that are actualy
> executed as commands by the shell...

You can fool this with

	X=anything rm -fr *

I prefer

	sh -x -n file.shar

Pat Wood
Pipeline Associates, Inc.
ihnp4!whuxn!phw5!phw
attunix!whuxn!phw5!phw