cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1995-02-10 - Re: why pgp sucks

Header Data

From: Erich von Hollander <erich@CSUA.Berkeley.EDU>
To: Derek Atkins <warlord@mit.edu>
Message Hash: eae362c34b86829f53c5d141b613407c6f292db4552974a03f5e7277163f68a6
Message ID: <199502102303.PAA24281@soda.CSUA.Berkeley.EDU>
Reply To: <9502102058.AA07955@josquin.media.mit.edu>
UTC Datetime: 1995-02-10 23:03:31 UTC
Raw Date: Fri, 10 Feb 95 15:03:31 PST

Raw message

From: Erich von Hollander <erich@CSUA.Berkeley.EDU>
Date: Fri, 10 Feb 95 15:03:31 PST
To: Derek Atkins <warlord@mit.edu>
Subject: Re: why pgp sucks
In-Reply-To: <9502102058.AA07955@josquin.media.mit.edu>
Message-ID: <199502102303.PAA24281@soda.CSUA.Berkeley.EDU>
MIME-Version: 1.0
Content-Type: text/plain


In message <9502102058.AA07955@josquin.media.mit.edu>, Derek Atkins writes:
>
>> if i use a command like
>> 
>> 	pgp filename
>
>The problem is that you are using the wrong command....

hal pointed out to me that

	pgp -F

will do exactly what i want.  it will work.  the behavior of pgp -F (given
keys, for instance) is not well-described in the docs, but it will do what i
want it to.

as hal said, i can catch the stdout for the data, and catch the stderr for
out-of-band info about the data, and this will work fine.

and the product of all this is going to be quite cool.  i'll post it when
it's finished.

e

Thread