OSSL_CRMF_MS...INFO_CERTREQ(3ossl)

🎀 OSSL_CRMF_MS...INFO_CERTREQ(3ossl) — OpenSSL manual page for CRMF Registration Info 🎀

okay bestie, welcome to the CRMF Registration Info corner of OpenSSL 💅 This page is your group chat for getting and setting regInfo on an OSSL_CRMF_MSG. The manual name is OSSL_CRMF_MS...INFO_CERTREQ(3ossl), and the actual function girlies are right below. let's get into it ✨

✨ NAME ✨

• OSSL_CRMF_MSG_get0_regInfo_utf8Pairs
• OSSL_CRMF_MSG_set1_regInfo_utf8Pairs
• OSSL_CRMF_MSG_get0_regInfo_certReq
• OSSL_CRMF_MSG_set1_regInfo_certReq

These are the functions getting or setting CRMF Registration Info. Periodt. 🫶

💖 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 🌸

• OSSL_CRMF_MSG_get0_regInfo_utf8Pairs() — gives you back the first utf8Pairs regInfo inside the given msg, if present. peek, don't touch.
• OSSL_CRMF_MSG_set1_regInfo_utf8Pairs() — takes a copy of the given utf8pairs value and adds it as utf8Pairs regInfo to the given msg. See RFC 4211 section 7.1. copy that over, bestie.
• OSSL_CRMF_MSG_get0_regInfo_certReq() — gives you back the first certReq regInfo inside the given msg, if present.
• OSSL_CRMF_MSG_set1_regInfo_certReq() — takes a copy of the given cr value and adds it as certReq regInfo to the given msg. See RFC 4211 section 7.2.

🦋 RETURN VALUES 🦋

All the get0_*() functions return the respective pointer value, and NULL if it's not present. All the set1_*() functions return 1 on success and 0 on error. That's the whole vibe check: pointer or NULL, 1 or 0. no cap.

🌈 NOTES 🌈

Calling the set1_*() functions multiple times adds multiple instances of the respective control to the regInfo structure of the given msg. So yes, they stack — the setter keeps adding.

Important vibe check: RFC 4211 expects multiple utf8Pairs in one regInfo structure, but it does not allow multiple certReq. Read that twice, bestie. 🫶

🧚 SEE ALSO 🧚

RFC 4211 — go read the source, it's iconic. 💫

👑 HISTORY 👑

The OpenSSL CRMF support was added in OpenSSL 3.0. So this whole CRMF situation has been around since OpenSSL 3.0, iykyk. 🎀

🎀 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>.

---

Stay hydrated, keep your regInfo close, and remember this is the 3.5.6 edition dated 2026-04-07 of OSSL_CRMF_MS...INFO_CERTREQ(3ossl). Mwah 💋✨