OSSL_CMP_STATUSINFO_NEW(3ossl)
β¨ OSSL_CMP_STATUSINFO_NEW β¨
okay bestie, welcome to the OSSL_CMP_STATUSINFO_NEW(3ossl) page π this is the part of the OpenSSL manual that handles the CMP PKIStatus situation, and honestly? it's giving quiet luxury. let's get into it.
πΈ NAME πΈ
OSSL_CMP_STATUSINFO_new, OSSL_CMP_snprint_PKIStatusInfo, OSSL_CMP_CTX_snprint_PKIStatus β the function squad that manages the CMP PKIStatus. no cap, that's the whole job description.
π SYNOPSIS π
#include <openssl/cmp.h>
OSSL_CMP_PKISI *OSSL_CMP_STATUSINFO_new(int status, int fail_info,
const char *text);
char *OSSL_CMP_snprint_PKIStatusInfo(const OSSL_CMP_PKISI *statusInfo,
char *buf, size_t bufsize);
char *OSSL_CMP_CTX_snprint_PKIStatus(const OSSL_CMP_CTX *ctx, char *buf,
size_t bufsize);
like look at those signatures. so clean. so demure. π«Ά
π DESCRIPTION π
so this whole thing is the PKIStatus API for using CMP (Certificate Management Protocol) with OpenSSL. main character energy fr fr.
OSSL_CMP_STATUSINFO_new()β makes a brand newPKIStatusInfostructure and fills in the values you hand it. it sets thestatusfield to status, copies text over tostatusString(unless text isNULL, in which case it justβ¦ doesn't π), and interprets fail_info as a bit pattern for thefailInfofield. slay.OSSL_CMP_snprint_PKIStatusInfo()β takes the statusInfo you give it, whips up a human-readable string representing it, and places that string into the given buffer, with the given maximal length. it's basically the glow-up translator β¨OSSL_CMP_CTX_snprint_PKIStatus()β same vibe, but for thePKIStatusInfocomponents of the CMP context ctx. human-readable string β given buffer β given maximal length. iconic.
π¦ NOTES π¦
CMP is defined in RFC 9810. that's the receipts, iykyk π
π RETURN VALUES π
OSSL_CMP_STATUSINFO_new()returns a pointer to the structure on success, orNULLon error. it either eats or it doesn't, there is no in between πOSSL_CMP_snprint_PKIStatusInfo()andOSSL_CMP_CTX_snprint_PKIStatus()return a copy of the buffer pointer containing the string, orNULLon error. so if you getNULL, that's your villain origin story right there.
π HISTORY π
the OpenSSL CMP support was added in OpenSSL 3.0. so it's not ancient, it's just β¨establishedβ¨.
π 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>.
real talk bestie: that's a license, not a suggestion. read it. respect it. it's the law π
okay that's the whole page, you ate that π mwah! this was the 3.5.9 version of the OSSL_CMP_STATUSINFO_NEW(3ossl) manual, dated 2026-09-29 β go forth and manage those statuses, queen πβ¨
π¦ where this page comes from
- fedora 43: openssl-devel 1:3.5.9-1.fc43 Β· Apache-2.0
- fedora 43: openssl-devel 1:3.5.9-1.fc43 Β· Apache-2.0
- fedora 44: openssl-devel 1:3.5.9-1.fc44 Β· Apache-2.0
- fedora 44: openssl-devel 1:3.5.9-1.fc44 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms