caam_read_rsa_crt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… caam_read_rsa_crt(9) β€” yes bestie, we're in the kernel API manual now

okay so picture this: it's caam_read_rsa_crt(9), straight out of the Kernel API Manual, and she is literally here to read your CRT members. πŸŽ€

✨ NAME ✨

caam_read_rsa_crt β€” the little function that's used for reading dP, dQ, and qInv CRT members. 🫢

and here's the tea: dP, dQ and qInv could decode to less than the corresponding p, q length, because the BER-encoding requires that the minimum number of bytes be used to encode the integer. so yeah β€” decoded dP, dQ, qInv values have to be zero-padded to the appropriate length. no cap, that's just how it is. πŸ’€

🌸 SYNOPSIS 🌸

u8 * caam_read_rsa_crt (const u8 *ptr , size_t nbytes , size_t dstlen );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ptr β€” pointer to {dP, dQ, qInv} CRT member. that's your girl, the thing we're reading πŸ’–
  • nbytes β€” length in bytes of {dP, dQ, qInv} CRT member. how many bytes we're working with, periodt ✨
  • dstlen β€” length in bytes of the corresponding p or q prime factor. the size we're padding out to πŸŽ€

πŸ‘‘ SEE ALSO πŸ‘‘


πŸ’œ friendly reminder bestie: those zero-padding rules aren't a suggestion, they're the whole point. the decoded CRT values have to be zero-padded to the appropriate length. don't skip it fr fr.

okay that's the whole page, slay. this icon lives in ./drivers/crypto/caam, dated October 2026, and it ate. πŸ’…βœ¨πŸŒˆ

πŸ“¦ where this page comes from