From: amp <Alan.Pugh@internetMCI.COM>
To: cypherpunks <cypherpunks@toad.com>
Message Hash: c4875b47acc0ea584481a0d269986d5297c5358abd1e32561ea7e27f2ee7fb2b
Message ID: <01HZQF02DX5U95Q5Q6@MAIL-CLUSTER.PCY.MCI.NET>
Reply To: N/A
UTC Datetime: 1996-01-07 20:36:55 UTC
Raw Date: Mon, 8 Jan 1996 04:36:55 +0800
From: amp <Alan.Pugh@internetMCI.COM>
Date: Mon, 8 Jan 1996 04:36:55 +0800
To: cypherpunks <cypherpunks@toad.com>
Subject: PGP 3.0
Message-ID: <01HZQF02DX5U95Q5Q6@MAIL-CLUSTER.PCY.MCI.NET>
MIME-Version: 1.0
Content-Type: text/plain
-- [ From: amp * EMC.Ver #2.3 ] --
-----BEGIN PGP SIGNED MESSAGE-----
Hello all,
I've seen a couple of messages here about possibilities of what might
be in pgp 3.0.
I am in agreement that keys should be expirable. I produce new keys
once a year anyway. This is probably excessive given my probable
threat models, but I think it lends itself well to having a sort of
time-stamp on documents. Given that it is true that I could keep a
copy of my unrevoked key after I've formally revoked it, I still
think that it is beneficial to have signed documnents produced over
time bear keys that are time-bound at least as far as the way I use
pgp.
The main point of this post was really to ask if there is a page or
rfc somewhere that describes what is expected to be in pgp 3.0. Is
there a particular reason that this to-be-released-with-source
program is shrouded in what appears to be secrecy?
As usual, I'm confused. It would help me greatly if I were able to
give people an idea of the added capabilities pgp will posess
whenever it is finally released. This isn't a flame as I'd like to
see it done right the first time rather than have it released then
see 4 or 5 different bug fixes quickly come out that confuse the
issue during its introduction. I found the FUD surrounding 2.6.x to
be hard to overcome with some people. <non-ob-crypto:> Heck, I found
a copy of pkz204e the other day on a pc in my office. The FUD
surrounding this product was pretty great if y'all recall. <back on
crypto:> I give talks occasionally about my company's internet
offerings for business. It would be nice to be able to speak of the
future of crypto with pgp with a bit more certainty.
Thanks for your time and consideration,
amp
<0003701548@mcimail.com> (since 10/31/88)
<alan.pugh@internetmci.com>
PGP Key = 57957C9D
PGP FP = FA 02 84 7D 82 57 78 E4 E2 1C 7B 88 62 A6 F9 F7
January 7, 1996 15:12
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQEVAwUBMPApK4dTfgZXlXydAQHRagf/dqF+gF41JYIBroUlmddgX6Lur3ISBxrl
MhtMAdcFzyBcRxrYIgPf+gkkzOqNSBeXHvwvZ/CWLuJpvbRXnCD0IL3hhoYGVIl5
UxvP2gh1M+wU7pEm6DYlQpq2z3OVxoG62LW6+v1YgVP6hHOEQNUYGn64TSFMDbdr
cU63c3pXLusBb6yLM5dKaPZDqo8y2YHo6hYDT21SW+Tx0MxOK7/diL9qfbBXyitk
8tmNmgti6V0MCatRAh0L4xc7kkDq33RXhyEgjTimTTwt0QIgV/QLAPN1Mdj/ZEoj
U599xGySNUfPXLwJz5mda0UDS3Pp1CNHpjdUzpFUbhDndSo1sh+ocA==
=cxUU
-----END PGP SIGNATURE-----
Return to January 1996
Return to “amp <Alan.Pugh@internetMCI.COM>”
1996-01-07 (Mon, 8 Jan 1996 04:36:55 +0800) - PGP 3.0 - amp <Alan.Pugh@internetMCI.COM>