[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CAN'T Re: MUST versus SHOULD in application decisions

To: ietf-open-pgp@xxxxxxx
Subject: Re: CAN'T Re: MUST versus SHOULD in application decisions
From: lutz@xxxxxxxxxxxxxxxxxxx (Lutz Donnerhacke)
Date: 30 Oct 1997 12:54:04 GMT
Newsgroups: iks.lists.ietf-open-pgp
Organization: IKS GmbH Jena
References: <>
Sender: owner-ietf-open-pgp@xxxxxxx

* Bill Stewart wrote:
>The problem is that PGP doesn't _do_ Storage or Communication;
>it takes a batch of input data, does crypto, and produces output data.

*grin* So recovery is not needed in any case.... The surrounding enviroment
has to provide extra storage functions for plaintext.

A simple solution. Thanx.

BTW: Please remove it from all PGP 5.x implementations. This allows us to
remove it from the draft.

References:
- CAN'T Re: MUST versus SHOULD in application decisions
  - From: Bill Stewart

Prev by Date: Re: CMR/ARR and OpenPGP
Next by Date: Re: Symmetric Algorithm
Previous by thread: CAN'T Re: MUST versus SHOULD in application decisions
Next by thread: do security recommendations belong in standard? (Re: CAN'T Re: MUST versus SHOULD in application decisions)
Index(es):
- Date
- Thread