OSSL_CRMF_MSG...GINFO_CERTREQ(3SSL)

📦
version 4.0.3 · 13 versions
, in ubuntu stonking

💖 OSSL_CRMF_MSG_get0_regInfo_utf8Pairs, OSSL_CRMF_MSG_set1_regInfo_utf8Pairs, OSSL_CRMF_MSG_get0_regInfo_certReq, OSSL_CRMF_MSG_set1_regInfo_certReq — NAME ✨

okay bestie so this is the OSSL_CRMF_MSG...GINFO_CERTREQ page from the OpenSSL manual (section 3SSL, we love a library page 🌸), and it's literally all about the functions that get or set the CRMF Registration Info. yes we're doing certificate request message format today, get into it 💅

🌈 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 🦋

so there's four functions and they're basically two little duos, and they GO together like this:

  • OSSL_CRMF_MSG_get0_regInfo_utf8Pairs() — hands you back the first utf8Pairs regInfo chillin' inside the given msg, if it's even there 👀
  • OSSL_CRMF_MSG_set1_regInfo_utf8Pairs() — drops a copy of the utf8pairs value you gave it into the given msg as a utf8Pairs regInfo. and like, go read RFC 4211 section 7.1 for the lore, iykyk 📖
  • OSSL_CRMF_MSG_get0_regInfo_certReq() — same energy, different field: gives you the first certReq regInfo in the given msg, if present 💫
  • OSSL_CRMF_MSG_set1_regInfo_certReq() — sticks a copy of your cr value in as a certReq regInfo on the given msg. RFC 4211 section 7.2 is where the deets live, periodt ✨

🎀 RETURN VALUES 🎀

  • All the get0_*() functions return the respective pointer value, and NULL if it's not present. no notes, that's the whole vibe 🫶
  • All the set1_*() functions return 1 on success, 0 on error. classic. iconic. we respect it 💅

🔥 NOTES 🔥

okay this is the part where you listen, bestie:

If you call the set1_*() functions multiple times, you get multiple instances of the respective control added into the regInfo structure of the given msg. so it just keeps stacking, like my unread notifications 😭

and the plot twist: RFC 4211 actually expects multiple utf8Pairs inside one regInfo structure, which is fine and cute and encouraged. BUT it does **not allow multiple certReq. so like, don't do that one. fr fr. that's the rule 🔥

🌟 SEE ALSO 🌟

👑 HISTORY 👑

The whole OpenSSL CRMF support situation walked in the door in OpenSSL 3.0. a glow-up era truly 💖

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, no cap 🧚💜 this was OpenSSL 4.0.3, dated 2026-09-2, and honestly? she ate. go forth and manage your regInfo responsibly 👑🌸

📦 where this page comes from