Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!houxm!whuxl!whuxlm!akgua!gatech!seismo!rochester!bullwinkle!uw-beaver!tikal!sigma!bill
From: bill@sigma.UUCP
Newsgroups: net.sources.bugs
Subject: Re: Beware of Blindly Un-SHARing a File
Message-ID: <698@sigma.UUCP>
Date: Sat, 19-Apr-86 18:24:50 EST
Article-I.D.: sigma.698
Posted: Sat Apr 19 18:24:50 1986
Date-Received: Wed, 23-Apr-86 12:28:40 EST
References: <406@bu-cs.UUCP> <455@gould9.UUCP>
Reply-To: bill@sigma.UUCP (William Swan)
Lines: 11

In article <455@gould9.UUCP> joel@gould9.UUCP (Joel West) writes:
>[...]
>Any posting of a Trojan Horse would immediately require that the
>offending site be removed from the net.  If the posting came in through
>a forgery, the site accepting the forgery would be required to take
>corrective actions (such as removing anonymous UUCP logins) or quit the net.
>[...]

Sounds like what you _really_ need is an "unshar.c" (to complement shar.c,
of course), that has a very limited command set, to avoid those Trojan
Horses.