From: Bryce Wilcox <wilcoxb@nagina.cs.colorado.edu>
Date: Fri, 25 Aug 95 19:12:45 PDT
To: "P.J. Ponder" <ponder@wane-leon-mail.scri.fsu.edu>
Subject: Re: Auto-pgp for pine/elm/tin (fwd)
In-Reply-To: <Pine.3.89.9508252137.H2413-0100000@wane3.scri.fsu.edu>
Message-ID: <199508260212.UAA27830@nagina.cs.colorado.edu>
MIME-Version: 1.0
Content-Type: text/plain



-----BEGIN PGP SIGNED MESSAGE-----

> I have PGP installed on my pc and if I want to 
> use it, I can save the message in ascii, then upload it to the server 
> where I have my Internet account, then mail it.


I use PGP on every outgoing message and about 20% of incoming messages.  And
I send/receive a *lot* of messages.  No way I would be able to do a process 
like the above on my mail.


In a few weeks I will be able to get mail on my home computer, but most
(80%?) Internet users will still not have that luxury.


>  maybe not entirely 
> transparent, but at least it seems to me that the convenience of running 
> it on the server with something like Mr. Wilcox's BAP is not worth the 
> added risk.


In my opinion it *is* worth the risk.  I believe that having "BEGIN PGP
SIGNED MESSAGE" in your posts and e-mail is a social good (raising public
awareness of/acceptance of PGP) which is more important than actually
protecting my e-mail from spying/forgery.


>  Besides, how often do you need to use it?  


Public awareness/acceptance, traffic analysis, the "electronic envelope" 
analogy...


If you don't use it, it's not doing any good at all.


Regards,

Bryce

signatures follow:


                                 +                                           
    public key on keyservers     /.       island Life in a chaos sea         
    or via finger 0x617c6db9     /             bryce.wilcox@colorado.edu     
                                 ---*                                     

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Auto-signed with Bryce's Auto-PGP v1.0beta

iQCVAwUBMD6C7/WZSllhfG25AQFQ7gP9EX48Bw6mZ5WJYR+4j78oPUL7++Irz39i
b6EbU8ZWUia1AEqSVLmKibIE4JOBejZKzSCCF4OrE7j+BCT1B5hLbIrUZzNNHDQk
pXbfLo51FyIsR4SlCYtWdsMUiAI08ACOAAxtab/3uC2DEO7UB/9A+xALPGNFQWdz
oRnku9NOOY0=
=0uru
-----END PGP SIGNATURE-----