From: “Patrick J. LoPresti” <patl@skyclad.lcs.mit.edu>
To: cypherpunks@toad.com
Message Hash: 6982f38804b7aea6fbf92da2170de9c341fbaa1f07168e993ae31678531f1700
Message ID: <199508221411.KAA00910@skyclad.lcs.mit.edu>
Reply To: <199508220140.TAA12229@nagina.cs.colorado.edu>
UTC Datetime: 1995-08-22 14:12:08 UTC
Raw Date: Tue, 22 Aug 95 07:12:08 PDT
From: "Patrick J. LoPresti" <patl@skyclad.lcs.mit.edu>
Date: Tue, 22 Aug 95 07:12:08 PDT
To: cypherpunks@toad.com
Subject: Re: Certificates/Anonymity/Policy/True Names
In-Reply-To: <199508220140.TAA12229@nagina.cs.colorado.edu>
Message-ID: <199508221411.KAA00910@skyclad.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "wilcoxb" == Bryce Wilcox <wilcoxb@nagina.cs.colorado.edu> writes:
>> Yes, I've been remiss. It's an old belief -- that signing is
>> expensive. Now that I'm using emacs extensions and RMAIL, it's
>> really easy -- but I still follow the old habit.
wilcoxb> I have a pretty easy-to-use set-up...
Probably not as easy as Carl's.
wilcoxb> Not to seem picky or anything, but now that I have a
wilcoxb> clearsigned message from you, I need your public key in
wilcoxb> order to verify it. :-)
Assuming Carl is using Mailcrypt under Emacs (as he suggests above),
then he doesn't have the same problem. When the signature fails to
verify for lack of a key, Mailcrypt will parse the PGP output and
offer to fetch the needed key automatically (and instantly) via HTTP
to the keyservers.
But then, Emacs only runs on "ghettoized" operating systems like Unix,
VMS, OS/2, and Windows 95...
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface
iQCVAwUBMDnljnr7ES8bepftAQEFLwP/b9TE5QphAhJl1PyhdAsbyE3Vx58TuwGD
dAJf2fpThN9wYgQ3b0K+QxYbLVcQTbof5v8/AvYyM32JrsEzRQXZmjguoOT0BnLz
gjxTS5qLhOmcOhbUc6G3iEPQTuusWU59PPqp1TYPkZ0zVopDvPjay2O60whl4t/a
bARjHknf+es=
=bAX+
-----END PGP SIGNATURE-----
Return to August 1995
Return to ““Patrick J. LoPresti” <patl@skyclad.lcs.mit.edu>”