Section 5.1 (fix garbled text):
old:
Note that when an implementation forms several PKESKs with one session key,
forming a message that can be decrypted by several keys, the PKCS-1 the
implementation MUST make new padding for each key.
new:
Note that when an implementation forms several PKESKs with one session key,
forming a message that can be decrypted by several keys, the implementation
MUST make new PKCS-1 padding for each key.
---
Section 4.2.2.1 (fix consistency):
old:
bodyLen = length_octet;
new:
bodyLen = 1st_octet;
---
Section 4.2.2.2 (fix consistency, clarify):
old:
bodyLen = (1st_octet - 192) * 256 + (2nd_octet) + 192
new:
bodyLen = ((1st_octet - 192) << 8) + (2nd_octet) + 192
---
Section 5.2.3.1 (fix consistency, clarify):
old:
The length includes the type octet but not this length. Its format
is the same as the "new" format packet header lengths. That is:
if the 1st octet < 192, then length is the octet value
if the 1st octet >= 192 and < 255, then length is 2 octets and
equal to (1st octet - 192) * 256 + (2nd octet) + 192
if the 1st octet = 255, then the subpacket length is a
four-octet scalar found in octets 2 through 5, as per the packet
header length.
new:
The length includes the type octet but not this length. Its format
is the same as the "new" format packet header lengths. That is:
if the 1st octet < 192, then
lengthOfLength = 1
subpacketLen = 1st_octet
if the 1st octet >= 192 and < 255, then
lengthOfLength = 2
subpacketLen = ((1st_octet - 192) << 8) + (2nd_octet) + 192
if the 1st octet = 255, then
lengthOfLength = 5
subpacket length = [four-octet scalar starting at 2nd_octet]
---
Section 4.2.1 (remove text):
old:
3 - The packet is of indeterminate length. The header is 1 octet
long, and the implementation must determine how long the packet
is. If the packet is in a file, this means that the packet
extends until the end of the file. With a compressed packet, the
algorithm implicitly denotes how the end of the packet. In
general, an implementation SHOULD NOT use indeterminate length
packets except where the end of the data will be clear from the
context, and even then it is better to use a definite length, or
a new-format header. The new-format headers described below have
a mechanism for precisely encoding data of indeterminite length.
new:
3 - The packet is of indeterminate length. The header is 1 octet
long, and the implementation must determine how long the packet
is. If the packet is in a file, this means that the packet
extends until the end of the file. In general, an implementation
SHOULD NOT use indeterminate length packets except where the end
of the data will be clear from the context, and even then it is
better to use a definite length, or a new-format header. The
new-format headers described below have a mechanism for
precisely encoding data of indeterminite length.