draft-ietf-openpgp-rfc2440bis-17.txt   draft-ietf-openpgp-rfc2440bis-18.txt 
Network Working Group Jon Callas Network Working Group Jon Callas
Category: INTERNET-DRAFT PGP Corporation Category: INTERNET-DRAFT PGP Corporation
draft-ietf-openpgp-rfc2440bis-17.txt draft-ietf-openpgp-rfc2440bis-18.txt
Expires November 2006 Lutz Donnerhacke Expires November 2006 Lutz Donnerhacke
May 2006 May 2006
Obsoletes: 1991, 2440 Hal Finney Obsoletes: 1991, 2440 Hal Finney
PGP Corporation PGP Corporation
David Shaw David Shaw
Rodney Thayer Rodney Thayer
OpenPGP Message Format OpenPGP Message Format
draft-ietf-openpgp-rfc2440bis-17.txt draft-ietf-openpgp-rfc2440bis-18.txt
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
IPR Claim Notice IPR Claim Notice
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
skipping to change at page 21, line 50 skipping to change at page 21, line 50
- MPI of DSA value r. - MPI of DSA value r.
- MPI of DSA value s. - MPI of DSA value s.
The signature calculation is based on a hash of the signed data, as The signature calculation is based on a hash of the signed data, as
described above. The details of the calculation are different for described above. The details of the calculation are different for
DSA signatures than for RSA signatures. DSA signatures than for RSA signatures.
With RSA signatures, the hash value is encoded as described in With RSA signatures, the hash value is encoded as described in
PKCS#1 section 9.2.1 encoded using PKCS-1 encoding type PKCS#1 section 9.2.1 encoded using PKCS#1 encoding type
EMSA-PKCS1-v1_5 as described in section 12.1. This requires EMSA-PKCS1-v1_5 as described in section 12.1. This requires
inserting the hash value as an octet string into an ASN.1 structure. inserting the hash value as an octet string into an ASN.1 structure.
The object identifier for the type of hash being used is included in The object identifier for the type of hash being used is included in
the structure. The hexadecimal representations for the currently the structure. The hexadecimal representations for the currently
defined hash algorithms are: defined hash algorithms are:
- MD5: 0x2A, 0x86, 0x48, 0x86, 0xF7, 0x0D, 0x02, 0x05 - MD5: 0x2A, 0x86, 0x48, 0x86, 0xF7, 0x0D, 0x02, 0x05
- RIPEMD-160: 0x2B, 0x24, 0x03, 0x02, 0x01 - RIPEMD-160: 0x2B, 0x24, 0x03, 0x02, 0x01
skipping to change at page 54, line 24 skipping to change at page 54, line 24
yDgBO22WxBHv7O8X7O/jygAEzol56iUKiXmV+XmpCtmpqQUKiQrFqclFqUDBovzS yDgBO22WxBHv7O8X7O/jygAEzol56iUKiXmV+XmpCtmpqQUKiQrFqclFqUDBovzS
vBSFjNSiVHsuAA== vBSFjNSiVHsuAA==
=njUN =njUN
-----END PGP MESSAGE----- -----END PGP MESSAGE-----
Note that this example has extra indenting; an actual armored Note that this example has extra indenting; an actual armored
message would have no leading whitespace. message would have no leading whitespace.
7. Cleartext signature framework 7. Cleartext signature framework
It is desirable to sign a textual octet stream without ASCII It is desirable to be able to sign a textual octet stream without
armoring the stream itself, so the signed text is still readable ASCII armoring the stream itself, so the signed text is still
without special software. In order to bind a signature to such a readable without special software. In order to bind a signature to
cleartext, this framework is used. (Note that this framework is not such a cleartext, this framework is used. (Note that this framework
intended to be reversible. RFC 3156 defines another way to sign is not intended to be reversible. RFC 3156 defines another way to
cleartext messages for environments that support MIME.) sign cleartext messages for environments that support MIME.)
The cleartext signed message consists of: The cleartext signed message consists of:
- The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
single line, single line,
- One or more "Hash" Armor Headers, - One or more "Hash" Armor Headers,
- Exactly one empty line not included into the message digest, - Exactly one empty line not included into the message digest,
skipping to change at page 75, line 46 skipping to change at page 75, line 46
[RFC2279] Yergeau., F., "UTF-8, a transformation format of [RFC2279] Yergeau., F., "UTF-8, a transformation format of
Unicode and ISO 10646", RFC 2279, January 1998. Unicode and ISO 10646", RFC 2279, January 1998.
[RFC2822] Resnick, P., "Internet Message Format", RFC 2822. [RFC2822] Resnick, P., "Internet Message Format", RFC 2822.
[RFC3156] M. Elkins, D. Del Torto, R. Levien, T. Roessler, [RFC3156] M. Elkins, D. Del Torto, R. Levien, T. Roessler,
"MIME Security with OpenPGP", RFC 3156, "MIME Security with OpenPGP", RFC 3156,
August 2001. August 2001.
[RFC3437] B. Kaliski and J. Staddon, " PKCS #1: RSA [RFC3447] B. Kaliski and J. Staddon, "PKCS #1: RSA
Cryptography Specifications Version 2.1", Cryptography Specifications Version 2.1",
RFC 2437, February 2003. RFC 3447, February 2003.
[SCHNEIER] Schneier, B., "Applied Cryptography Second Edition: [SCHNEIER] Schneier, B., "Applied Cryptography Second Edition:
protocols, algorithms, and source code in C", 1996. protocols, algorithms, and source code in C", 1996.
[TWOFISH] B. Schneier, J. Kelsey, D. Whiting, D. Wagner, C. [TWOFISH] B. Schneier, J. Kelsey, D. Whiting, D. Wagner, C.
Hall, and N. Ferguson, "The Twofish Encryption Hall, and N. Ferguson, "The Twofish Encryption
Algorithm", John Wiley & Sons, 1999. Algorithm", John Wiley & Sons, 1999.
17. References (Informative) 17. References (Informative)
 End of changes. 6 change blocks. 
11 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.30. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/