>> On Tue 12/05/09 1:14 PM , Harm Verhagen [email protected] >> <harm.verhagen%[email protected]> sent: ... >>When carefully reading chapter 7.2.1 encryption >>It describes how to generate the ciphertext representative c. (an integer) >>And then how to encode that integer using I2OSP which is described in 4.1. >>Reading chapter 4.1 I2OSP >>It states that the encrypted output is an octet string >>X = X_1 X_2 ... X_xLen. >>Where X_1 is the least significant octet of the ciphertext representative.
Carl wrote: >4 Data Conversion primitives >... >For the purposes of this document, and consistent with ASN.1 syntax, an octet >string is an ordered sequence of octets (eight-bit bytes). The sequence is >ordered from first (conventionally, leftmost) to last (rightmost). For pupose >to and from integers, the first octet is considered the most significant in the >following conversion primitives. > >Looks fairly straightforward to me... Also MS "admits" that they are wrong >implictly by stating that the bytes must be reversed for interoperability with >just about everything else... Right, and in the next chapter 4.1 I2OSP it is described how to do that exactly, and they describe (in detail) the opposite. I think I understand where the confusion comes from :) Harm
