Subject: Re: Encryption

From: David L Miller <[email-masked]>
Date: Mon, 1 Aug 1994 15:04:13 -0700 (PDT)

Pine will support encryption in the future, but the exact implementation is
still up in the air.  Suggestions and comments are welcome... 

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

On 27 Jul 1994, Billy Barron wrote:

> I suspect this is a can of worms post, but here it goes.  :-)  I am
> wondering what the plans are for PINE and encryption.  Is PGP, PEM,
> an API or none of the above the direction that PINE is going to take?
> We have a new committee on electronic forms being formed right now
> and I think they are leaning towards PEM.
> 
> By the way, if any of the ISA Corp people read this, what is the
> direction of ECS Mail?
> 
> Thanks,
> 
> 
> --
> Billy Barron,  Network Services Manager, Univ of Texas at Dallas
> [email-masked] 
> 
>

---

From: [email-masked] (J. Kelly Cunningham)
Date: 5 Aug 94 19:04:41 MDT

In article <[email-masked]>,
>> By the way, if any of the ISA Corp people read this, what is the
 
Until then, I have a c-shell script (inspired by mkpgp) you can use as an 
interface to pgp.

In a compose window you:
 
            use the editor of your choice,
            send encrypted attachments (as .tar.Z.uu in the message text, 
            encrypt a message,
            sign a message.
            
In a reply/forward you:
 
	    use the editor of your choice,
            decrypt, 
            extract encrypted attachments from the message text, 
            check signatures, 
            add public keys.

You can get it by  (1) sending your pgp public key to 
[email-masked] with (2) a promise not to 
laugh out loud at the code. 

          (I'm not much of a programmer :-)

-- kc