D2I_CMS_CONTENTINFO(3)

📦 version 4.4.0, in alpine 3.24, arch rolling

💅 D2I_CMS_CONTENTINFO 💅

okay so bestie, this is a page from the Library Functions Manual, section 3 — and it's all about the libcrypto girlies who turn Cryptographic Message Syntax data into bytes and back again. ✨

🌸 NAME 🌸

d2i_CMS_ContentInfo, i2d_CMS_ContentInfo, d2i_CMS_bio, i2d_CMS_bio, d2i_CMS_ReceiptRequest, i2d_CMS_ReceiptRequest — decode and encode Cryptographic Message Syntax data 🎀

🦋 SYNOPSIS 🦋

library “libcrypto”

#include <openssl/cms.h>
CMS_ContentInfo *
d2i_CMS_ContentInfo(CMS_ContentInfo **val_out,
    const unsigned char **der_in, long length);

int
i2d_CMS_ContentInfo(CMS_ContentInfo *val_in, unsigned char **out);

CMS_ContentInfo *
d2i_CMS_bio(BIO *in_bio, CMS_ContentInfo **val_out);

int
i2d_CMS_bio(BIO *out_bio, CMS_ContentInfo *val_in);

CMS_ReceiptRequest *
d2i_CMS_ReceiptRequest(CMS_ReceiptRequest **val_out,
    const unsigned char **der_in, long length);

int
i2d_CMS_ReceiptRequest(CMS_ReceiptRequest *val_in, unsigned char **out);

💖 DESCRIPTION 💖

so these functions are literally the decode-and-encode duo for Cryptographic Message Syntax data structures. that's their whole job. 💅

okay but fr, for the details about the semantics, examples, caveats, and bugs — go read ASN1_item_d2i(3). that's where the lore lives. 📖

d2i_CMS_ContentInfo() and i2d_CMS_ContentInfo() decode and encode a CMS_ContentInfo structure defined in RFC 5652 section 3. iconic. 👑

d2i_CMS_bio() and i2d_CMS_bio() are similar except that they decode or encode using a BIO pointer. same energy, different doorway. 🚪✨

d2i_CMS_ReceiptRequest() and i2d_CMS_ReceiptRequest() decode and encode a CMS_ReceiptRequest structure defined in RFC 2634 section 2.7. receipts! literally. 🧾

⭐ RETURN VALUES ⭐

  • d2i_CMS_ContentInfo() and d2i_CMS_bio() return a valid CMS_ContentInfo structure — or NULL if an error occurs. 😭
  • d2i_CMS_ReceiptRequest() returns a valid CMS_ReceiptRequest structure — or NULL if an error occurs. 🙈
  • i2d_CMS_ContentInfo() and i2d_CMS_ReceiptRequest() return the number of bytes successfully encoded, or a negative value if an error occurs. 🔥
  • i2d_CMS_bio() returns 1 for success or 0 if an error occurs. periodt. 💀
  • For all functions, the error code can be obtained by ERR_get_error(3). that's your girl when things go sideways. 🫶

👀 SEE ALSO 👀

🌈 STANDARDS 🌈

  • RFC 5652: Cryptographic Message Syntax, section 3: General Syntax
  • RFC 2634: Enhanced Security Services for S/MIME, section 2.7: Receipt Request Syntax

🎀 HISTORY 🎀

These functions first appeared in OpenSSL 0.9.8h and have been available since OpenBSD 6.7. she's been on the scene for a minute, ngl. 💜

and that's the whole vibe check 🧚💖 — sourced from Debian, dated June 8, 2025, page D2I_CMS_CONTENTINFO(3). slay, you're welcome, mwah 🍓💅

📦 where this page comes from