Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 exptools; site ihlpl.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ihnp4!ihlpl!bde
From: bde@ihlpl.UUCP (Ewbank)
Newsgroups: net.news.adm,net.news.sa,net.sources.d,net.wanted.sources
Subject: Re: Beware of Blindly Un-SHARing a File
Message-ID: <850@ihlpl.UUCP>
Date: Thu, 17-Apr-86 14:06:47 EST
Article-I.D.: ihlpl.850
Posted: Thu Apr 17 14:06:47 1986
Date-Received: Fri, 18-Apr-86 20:52:54 EST
References: <947@kitty.UUCP> <2407@prls.UUCP> <1439@garfield.columbia.edu>
Organization: AT&T Bell Laboratories
Lines: 23
Xref: watmath net.news.adm:600 net.news.sa:269 net.sources.d:117 net.wanted.sources:2178

> > [comments on April Fools Joke(?)]
> [brainstorming on how to shar safely]

what about a different approach.  post (on mod.sources) a pair of
programs, multiplex and demultiplex.  instead of using shar archives,
use these to post and extract programs from net.sources etc.

Multiplex would take a list of file names, and produce (for instance)
a file that contained lines starting with "F" and lines starting with
"D".  A line starting with "F" would indicate that this is a new file,
and the rest of the line would be the file name.  Lines starting with
a "D" would contain data to be placed in the most recently named file.

Demultiplex would take a file output from multiplex, and create the
given files.  Require relative pathnames.  Maybe only file names
instead of paths.

This would allow the same ability to transmit files without the danger
of malecious mischief.
-- 
"experience is what you get when you don't get anything else"
-- Bryan Ewbank, 312/979-4296, ...!ihnp4!ihlpl!bde,
   ih 6M-523 / AT&T Bell Labs / Naperville, IL  60566 / USA