IETF Logo Mail Archive

Conventional Encryption Keys, 5.3

nospam-seesignature@ceddec.com Thu, 26 March 1998 19:59 UTC

Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.7.3) id LAA25602 for ietf-open-pgp-bks; Thu, 26 Mar 1998 11:59:44 -0800 (PST)
Received: from ceddec.com (brickwall.ceddec.com [207.91.200.193]) by mail.proper.com (8.8.8/8.7.3) with ESMTP id LAA25598 for <ietf-open-pgp@imc.org>; Thu, 26 Mar 1998 11:59:43 -0800 (PST)
Received: by brickwall.ceddec.com id <43009>; Thu, 26 Mar 1998 15:00:33 -0500
Date: Thu, 26 Mar 1998 14:59:44 -0500
From: nospam-seesignature@ceddec.com
X-Sender: nobody@mars
To: ietf-open-pgp@imc.org
Subject: Conventional Encryption Keys, 5.3
In-Reply-To: <98Mar26.141225est.43009@brickwall.ceddec.com>
Message-Id: <98Mar26.150033est.43009@brickwall.ceddec.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ietf-open-pgp@imc.org
Precedence: bulk

I can create a conventional encryption key using S2K by itself on a
passphrase, but I can also encrypt a conventional key using a S2K on a
passphrase.

In the section beginning:

"The decryption result consists of a one-octet algorithm..."

Shouldn't there also be a two-octet checksum after the random key material
(to be identical to what is public-key encrypted)? 

--- reply to tzeruch - at - ceddec - dot - com ---

v2.43.4 | Report a Bug | By Email | System Status