RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 4880, "OpenPGP Message Format", November 2007

Source of RFC: openpgp (sec)

Errata ID: 2199
Status: Held for Document Update
Type: Technical

Reported By: Constantin Hagemeier
Date Reported: 2010-04-28
Held for Document Update by: Sean Turner

Section 3.7.2.1. says:

For compatibility, when an S2K specifier is used, the special value
254 or 255 is stored in the position where the hash algorithm octet
would have been in the old data structure.  This is then followed
immediately by a one-octet algorithm identifier, and then by the S2K
specifier as encoded above.

It should say:

For compatibility, when an S2K specifier is used, the special value
254 or 255 is stored in the position where the cipher algorithm octet
would have been in the old data structure.  This is then followed
immediately by a one-octet cipher algorithm identifier, and then by
the S2K specifier as encoded above.

Notes:

The paragraph before says:
Older versions of PGP just stored a cipher algorithm octet preceding
the secret data or a zero to indicate that the secret data was
unencrypted. The MD5 hash function was always used to convert the
passphrase to a key for the specified cipher algorithm.

Report New Errata