OSSL_CRMF_MS...INFO_CERTREQ(3ossl)

✨ NAME ✨

okay so this page is all about the OSSL_CRMF_MSG_get0_regInfo_utf8Pairs, OSSL_CRMF_MSG_set1_regInfo_utf8Pairs, OSSL_CRMF_MSG_get0_regInfo_certReq, and OSSL_CRMF_MSG_set1_regInfo_certReq girlies — they're the functions that get or set the CRMF Registration Info 💅 (and yes bestie, this is an OpenSSL 3ossl manual page, we're in the big leagues now 👑)

---

🌸 SYNOPSIS 🌸

#include <openssl/crmf.h>

ASN1_UTF8STRING
    *OSSL_CRMF_MSG_get0_regInfo_utf8Pairs(const OSSL_CRMF_MSG *msg);
int OSSL_CRMF_MSG_set1_regInfo_utf8Pairs(OSSL_CRMF_MSG *msg,
                                         const ASN1_UTF8STRING *utf8pairs);
OSSL_CRMF_CERTREQUEST
    *OSSL_CRMF_MSG_get0_regInfo_certReq(const OSSL_CRMF_MSG *msg);
int OSSL_CRMF_MSG_set1_regInfo_certReq(OSSL_CRMF_MSG *msg,
                                       const OSSL_CRMF_CERTREQUEST *cr);

---

🦋 DESCRIPTION 🦋

okay so like, four functions, two vibes — getters and setters, and they're all about regInfo 🎀

• OSSL_CRMF_MSG_get0_regInfo_utf8Pairs() — hands you back the first utf8Pairs regInfo inside the given msg, if it's even there. no copy, no drama, just the pointer, iykyk 🫶
• OSSL_CRMF_MSG_set1_regInfo_utf8Pairs() — takes a copy of the utf8pairs value you pass in and adds it as a utf8Pairs regInfo to msg. it's giving "duplicate and file it" energy ✨ see RFC 4211 section 7.1 for the receipts 📜
• OSSL_CRMF_MSG_get0_regInfo_certReq() — returns the first certReq regInfo in the given msg, if present. same deal as above, just the certReq flavor 💜
• OSSL_CRMF_MSG_set1_regInfo_certReq() — adds a copy of the given cr value as a certReq regInfo to msg. see RFC 4211 section 7.2 📜

---

🌈 RETURN VALUES 🌈

• all the get0_*() girlies return the respective pointer value — and NULL if it's not present 🙈 (no value, no problem, no pointer)
• all the set1_*() functions return 1 on success and 0 on error. that's it, that's the vibe check 💀

---

💀 NOTES 💀

⚠️ okay listen up bestie, this part matters ⚠️

if you call the set1_*() functions multiple times, you get multiple instances of the respective control piled into the regInfo structure of the given msg. so like, it stacks. 🫠

and here's the tea ☕ — RFC 4211 expects multiple utf8Pairs in one regInfo structure (so stacking those is fine, iconic even 💅), but it does not allow multiple certReq. so don't be out here adding certReq over and over, fr fr 😭

---

🔥 SEE ALSO 🔥

• RFC 4211 📖

---

⭐ HISTORY ⭐

the OpenSSL CRMF support showed up in OpenSSL 3.0 — a whole era, honestly 🎀✨

---

👑 COPYRIGHT 👑

Copyright 2007-2021 The OpenSSL Project Authors. All Rights Reserved. 💖

Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>.

---

okay that's the whole page, bestie, slay 🧚‍♀️ this was version 3.5.0, dated 2026-09-25, and brought to you by the OSSL_CRMF_MS...INFO_CERTREQ(3ossl) manual — go forth and register your info responsibly 💜🌸