From: “Sean A. Walberg” <sean@escape.ca>
To: cjl <cjl@welchlink.welch.jhu.edu>
Message Hash: 7845cdfee8c829b8126a2be5f8dbf42fc167c46a79129742f86f54639622db10
Message ID: <Pine.SOL.3.91.950823111838.20013C-100000@wpg-01.escape.ca>
Reply To: <Pine.SOL.3.91.950823114854.14341A-100000@welchlink.welch.jhu.edu>
UTC Datetime: 1995-08-23 16:24:58 UTC
Raw Date: Wed, 23 Aug 95 09:24:58 PDT
From: "Sean A. Walberg" <sean@escape.ca>
Date: Wed, 23 Aug 95 09:24:58 PDT
To: cjl <cjl@welchlink.welch.jhu.edu>
Subject: Re: PGP for pine/PINESIGN 2.0
In-Reply-To: <Pine.SOL.3.91.950823114854.14341A-100000@welchlink.welch.jhu.edu>
Message-ID: <Pine.SOL.3.91.950823111838.20013C-100000@wpg-01.escape.ca>
MIME-Version: 1.0
Content-Type: text/plain
-----BEGIN PGP SIGNED MESSAGE-----
I use mkpgp. It is a script that requres a lot of setting up, but once
you learn what you are doing it makes sense. Depending on how you want
it, it can be totally transparent. Personally, I took it off of total
transparency, and now use it by invoking it with Atl-&
I lost the site where I got it from, but I have it on disk if anybody
wants it sent. It includes instructions, and once it is going is totally
slick.
Sean
o-------------------o----------------------o-----------------------o
| Sean Walberg, | Tech Support | Pas_al, _obol, BASI_, |
| sean@escape.ca | escape communication | PostS_ript, T_L... |
| Mail for PGP key | 925-4290 | C fills all the holes |
o----------------] http://www.escape.ca/~sean [--------------------o
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBMDtVmt82JgvRKzQZAQGkAwP/cZU3+P2I6HB1fso4b1acv9O/QZWmPBw7
paP1jvkn0Vs9mU3yfF5kbvv6v7o/RMgm21+v/TVxnWnPnvDbHbqG/qnJmSHo1bhZ
lAoq26iwD1Urg8HXVPbnOti8PrboF2J5/cBIyQyC7tXtNI9t+ZgFu8V90QmPOHLl
wuhvOaHPjAg=
=iR37
-----END PGP SIGNATURE-----
Return to August 1995
Return to “Tatu Ylonen <ylo@cs.hut.fi>”