…ng these algorithms is performed according to the RSASSA-PKCS1-v1_5 scheme in [ RFC8017 ] using SHA-2 [ SHS ] as hash. For the algorithm "rsa-sha2-256", the hash used is SHA-256. For the algorithm "rsa-sha2-512", the hash used is SHA-512. The resulting signature is encoded as fol…

… a byte string that is the resulting signature. Using the function defined in [ RFC8017 ], the signature is: Signature = I2OSP(R, n) | I2OSP(S, n) where n = ceiling(key_length / 8) When using a COSE key for this algorithm, the following checks are made: o The 'kty' field MUST be …

…m a byte string that is the resulting signature. Using the function defined in [RFC8017], the signature is: Signature = I2OSP(R, n) | I2OSP(S, n) where n = ceiling(key_length / 8) When using a COSE key for this algorithm, the following checks are made: o The 'kty' field MUST be p…

…exception is raised if the inputs are not the same length. I2OSP and OS2IP from RFC8017 , which are used, respectively, to convert a non-negative integer to a byte string and convert a byte string to a non-negative integer. next_power_of_2(n: Unsigned) -> Unsigned returns the sma…

…ed to convert a byte string to and from a non-negative integer as described in [RFC8017]. (Note that these functions operate on byte strings in big-endian byte order.) * a || b: denotes the concatenation of byte strings a and b. For example, "ABC" || "DEF" == "ABCDEF". * substr(s…

… a byte string that is the resulting signature. Using the function defined in [ RFC8017 ], the signature is: Signature = I2OSP(R, n) | I2OSP(S, n) where n = ceiling(key_length / 8) When using a COSE key for this algorithm, the following checks are made: o The 'kty' field MUST be …

…or technical updates in PKCS #1 v2.2 compared to v2.1, and to the corresponding RFC8017 compared to RFC3447. PKCS #1 v2.2 got the correct update, but RFC8017 didn't -- presumably a copy-and-paste error. My oversight in reviewing the edits. Thanks, Joost, for pointing it out. Erra…

…or technical updates in PKCS #1 v2.2 compared to v2.1, and to the corresponding RFC8017 compared to RFC3447. PKCS #1 v2.2 got the correct update, but RFC8017 didn't -- presumably a copy-and-paste error. My oversight in reviewing the edits. Thanks, Joost, for pointing it out. Erra…