CTLOG_STORE_NEW(3ossl)
okay bestie, welcome to the CTLOG_STORE_NEW(3ossl) page β it's giving Certificate Transparency log list realness, and honestly? iconic. π
We're making a container for CT logs, filling it up, and freeing it when we're done. No cap.
β¨ NAME β¨
Create and populate a Certificate Transparency log list β that's the whole assignment, fr fr. The besties doing it are:
CTLOG_STORE_new_exCTLOG_STORE_newCTLOG_STORE_freeCTLOG_STORE_load_default_fileCTLOG_STORE_load_file
πΈ SYNOPSIS πΈ
#include <openssl/ct.h>
CTLOG_STORE *CTLOG_STORE_new_ex(OSSL_LIB_CTX *libctx, const char *propq);
CTLOG_STORE *CTLOG_STORE_new(void);
void CTLOG_STORE_free(CTLOG_STORE *store);
int CTLOG_STORE_load_default_file(CTLOG_STORE *store);
int CTLOG_STORE_load_file(CTLOG_STORE *store, const char *file);
π DESCRIPTION π
A CTLOG_STORE is a container for a list of CTLOGs (Certificate Transparency logs). The list can be loaded from one or more files and then searched by LogID (see RFC 6962, Section 3.2, for the definition of a LogID). It's literally the group chat of CT logs. π«Ά
CTLOG_STORE_new_ex() creates an empty list of CT logs associated with the library context libctx and the property query string propq. CTLOG_STORE_new() does the same thing as CTLOG_STORE_new_ex() but with the default library context and property query string. Lowkey the cozy defaults, slay. β¨
The CTLOG_STORE is then populated by CTLOG_STORE_load_default_file() or CTLOG_STORE_load_file(). CTLOG_STORE_load_default_file() loads from the default file, which is named ct_log_list.cnf in OPENSSLDIR (see the output of openssl-version(1)). This can be overridden using an environment variable named CTLOG_FILE. CTLOG_STORE_load_file() loads from a caller-specified file path instead. Both of these functions append any loaded CT logs to the CTLOG_STORE. The way they just keep adding? Obsessed. π
The expected format of the file is:
enabled_logs=foo,bar
[foo]
description = Log 1
key = <base64-encoded DER SubjectPublicKeyInfo here>
[bar]
description = Log 2
key = <base64-encoded DER SubjectPublicKeyInfo here>
Once a CTLOG_STORE is no longer required, it should be passed to CTLOG_STORE_free(). This will delete all of the CTLOGs stored within, along with the CTLOG_STORE itself. If the argument is NULL, nothing is done. Cleanup main character energy. π§Ή periodt.
π¦ NOTES π¦
If there are any invalid CT logs in a file, they are skipped and the remaining valid logs will still be added to the CTLOG_STORE. A CT log will be considered invalid if it is missing a "key" or "description" field. So yes, the valid girlies still get in β ngl, that's kind of ate. π
π RETURN VALUES π
Both CTLOG_STORE_load_default_file and CTLOG_STORE_load_file return 1 if all CT logs in the file are successfully parsed and loaded, 0 otherwise. That's the whole vibe check: 1 slays, 0 does not. π
π SEE ALSO π
β HISTORY β
CTLOG_STORE_new_ex was added in OpenSSL 3.0. All other functions were added in OpenSSL 1.1.0. Lore unlocked. π
π COPYRIGHT π
Copyright 2016-2024 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>.
This page is from OpenSSL 3.5.6, dated 2026-04-07 β bye bestie, go populate that log list! ππ
π¦ where this page comes from
- freebsd 15.1: base 15.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms