Thu, 03 October 1996 12:24 UTC

Received: from cnri by ietf.org id aa01576; 3 Oct 96 8:24 EDT
Received: from neptune.hq.tis.com by CNRI.Reston.VA.US id aa08198; 3 Oct 96 8:24 EDT
Received: from neptune.tis.com by neptune.TIS.COM id aa03062; 3 Oct 96 7:48 EDT
Received: from relay.hq.tis.com by neptune.TIS.COM id aa24111; 2 Oct 96 16:29 EDT
Received: by relay.hq.tis.com; id QAA06680; Wed, 2 Oct 1996 16:33:26 -0400
Received: from sol.hq.tis.com(10.33.1.100) by relay.tis.com via smap (V3.1.1) id xma006654; Wed, 2 Oct 96 16:32:56 -0400
Received: from relay.hq.tis.com by tis.com (4.1/SUN-5.64) id AA03144; Wed, 2 Oct 96 16:35:02 EDT
Received: by relay.hq.tis.com; id QAA06644; Wed, 2 Oct 1996 16:32:54 -0400
Received: from charon.mit.edu(18.70.0.224) by relay.tis.com via smap (V3.1.1) id xma006621; Wed, 2 Oct 96 16:32:27 -0400
Received: (from warlord@localhost) by charon.MIT.EDU (8.6.13/2.3JIK) id
X-Message-ID:
Message-ID: <20150415230917.23538.71272.ARCHIVE@ietfa.amsl.com>
X-Date: (the original message had no date)
Date: Thu, 03 Oct 1996 19:24:00 -0000

QAA25998; Wed, 2 Oct 1996 16:34:30 -0400
Message-Id: <199610022034.QAA25998@charon.MIT.EDU>
To: Peter Williams <peter@verisign.com>
Cc: "pem-dev@tis.com" <pem-dev@tis.com>, 
    "'Frederik H. Andersen'" <fha@dde.dk>
Subject: Re: Sad situation!!! 
In-Reply-To: Your message of "Wed, 02 Oct 1996 11:19:41 PDT."
             <9610021443.aa21905@neptune.TIS.COM> 
Date: Wed, 02 Oct 1996 16:34:27 EDT
From: Derek Atkins <warlord@athena.mit.edu>
Sender: pem-dev-approval@neptune.tis.com
Precedence: bulk

Peter,

You are confused.

It is possible for PGP to support message recovery systems (I don't
say "key" recovery, even though what I mean is that the session key
can be recovered).  The means to do this is 100% backwards compatible,
and can even be done using PGP 2.6.2.

The question is what the "corporate market" wants in terms of key/data
recovery mechanisms.

In my discussions with corporate markets, their recovery requirements
can be easily fulfilled by PGP.  So, saying that PGP cannot perform
data recovery is wrong; you just need to properly use (or configure,
as the case may be) the program.

As for the status of PGP 3.0 (aka PGPlib) -- we're trying to finish up
and get "alpha" quality code REAL soon.  The PGP Library is about 98%
finished, and the PGP message processing application hasn't changed in
a long time.  The PGP Key Management application is still being
flushed out.

-derek

  •