OSSL_STORE_OPEN(3ossl)
π OSSL_STORE_OPEN π
okay bestie, so this is the OpenSSL page for OSSL_STORE_OPEN(3ossl) β yes the manpage literally goes by OSSL_STORE_OPEN even though it's a whole squad of types and functions. it's giving ensemble cast energy π we're talking OSSL_STORE_CTX, OSSL_STORE_post_process_info_fn, OSSL_STORE_open, OSSL_STORE_open_ex, OSSL_STORE_ctrl, OSSL_STORE_load, OSSL_STORE_eof, OSSL_STORE_delete, OSSL_STORE_error and OSSL_STORE_close β all here to read objects from a URI. no cap. β¨
πΈ NAME πΈ
OSSL_STORE_CTX, OSSL_STORE_post_process_info_fn, OSSL_STORE_open, OSSL_STORE_open_ex, OSSL_STORE_ctrl, OSSL_STORE_load, OSSL_STORE_eof, OSSL_STORE_delete, OSSL_STORE_error, OSSL_STORE_close β types and functions to read objects from a URI. that's the whole vibe. π¦
β¨ SYNOPSIS β¨
#include <openssl/store.h>
typedef struct ossl_store_ctx_st OSSL_STORE_CTX;
typedef OSSL_STORE_INFO *(*OSSL_STORE_post_process_info_fn)(OSSL_STORE_INFO *,
void *);
OSSL_STORE_CTX *OSSL_STORE_open(const char *uri, const UI_METHOD *ui_method,
void *ui_data,
OSSL_STORE_post_process_info_fn post_process,
void *post_process_data);
OSSL_STORE_CTX *
OSSL_STORE_open_ex(const char *uri, OSSL_LIB_CTX *libctx, const char *propq,
const UI_METHOD *ui_method, void *ui_data,
const OSSL_PARAM params[],
OSSL_STORE_post_process_info_fn post_process,
void *post_process_data);
OSSL_STORE_INFO *OSSL_STORE_load(OSSL_STORE_CTX *ctx);
int OSSL_STORE_eof(OSSL_STORE_CTX *ctx);
int OSSL_STORE_delete(const char *uri, OSSL_LIB_CTX *libctx, const char *propq,
const UI_METHOD *ui_method, void *ui_data,
const OSSL_PARAM params[]);
int OSSL_STORE_error(OSSL_STORE_CTX *ctx);
int OSSL_STORE_close(OSSL_STORE_CTX *ctx);
and now the deprecated one, bestie. the following function has been deprecated since OpenSSL 3.0, and it can be hidden entirely by defining OPENSSL_API_COMPAT with a suitable version value, see openssl_user_macros(7):
int OSSL_STORE_ctrl(OSSL_STORE_CTX *ctx, int cmd, ... /* args */);
heads up:OSSL_STORE_ctrlis deprecated fr fr. if you setOPENSSL_API_COMPATto the right version it just... vanishes. poof. π
π DESCRIPTION π
so here's the tea: these functions help the application fetch supported objects β and if you wanna know which objects count as supported, go peek at "SUPPORTED OBJECTS" in OSSL_STORE_INFO(3) β from a given URI. π
the general method is a whole little ritual, and it goes like this:
- "open" the URI using
OSSL_STORE_open() - read each available and supported object using
OSSL_STORE_load()β keep going as long asOSSL_STORE_eof()hasn't been reached - finish it off with
OSSL_STORE_close()
and everything you retrieved lives inside an OSSL_STORE_INFO, which gets further described in OSSL_STORE_INFO(3). π
π§ Types
OSSL_STORE_CTX is a context variable that holds all the internal information for OSSL_STORE_open(), OSSL_STORE_open_ex(), OSSL_STORE_load(), OSSL_STORE_eof() and OSSL_STORE_close() to work together. it's the group chat they all share. main character energy, honestly. π
π Functions
OSSL_STORE_open_ex()β takes a uri or path uri, password UI method ui_method with associated data ui_data, and post processing callback post_process with associated data post_process_data, a library context libctx with an associated property query propq, and opens a channel to the data located at the URI. returns anOSSL_STORE_CTXwith all necessary internal information. the given ui_method and ui_data get reused by all functions that useOSSL_STORE_CTXwhen interaction is needed β for instance to provide a password. the auxiliaryOSSL_PARAM(3)parameters in params can be set to further modify the store operation. the given post_process and post_process_data get reused byOSSL_STORE_load()to manipulate or drop the value to be returned. and here's the fun part: the post_process function drops values by returningNULL, which causesOSSL_STORE_load()to start its process over with loading the next object β over and over β until post_process returns something other thanNULL, or the end of data is reached as indicated byOSSL_STORE_eof(). iconic little loop. πOSSL_STORE_open()β similar toOSSL_STORE_open_ex()but usesNULLfor the params, the library context libctx and property query propq. the low-effort version, and honestly? valid. π«ΆOSSL_STORE_ctrl()β takes anOSSL_STORE_CTX, and command number cmd and more arguments not specified here. the available loader specific command numbers and the arguments they each take depends on the loader that's used, and is documented together with that loader. iykyk. π
there are also global controls available:
OSSL_STORE_C_USE_SECMEMβ controls if the loader should attempt to use secure memory for any allocatedOSSL_STORE_INFOand its contents. this control expects one argument, a pointer to anintthat is expected to have the value1(yes) or0(no). any other value is an error. so like...1or0, bestie. don't get cute with it. πOSSL_STORE_load()β takes anOSSL_STORE_CTXand tries to load the next available object and return it wrapped withOSSL_STORE_INFO. πOSSL_STORE_delete()β deletes the object identified by uri. bye bye object πOSSL_STORE_eof()β takes anOSSL_STORE_CTXand checks if we've reached the end of data. are we there yet? π€OSSL_STORE_error()β takes anOSSL_STORE_CTXand checks if an error occurred in the lastOSSL_STORE_load()call. note: it may still be meaningful to try and load more objects, unlessOSSL_STORE_eof()shows that the end of data has been reached. so don't panic-quit on the first oopsie. πOSSL_STORE_close()β takes anOSSL_STORE_CTX, closes the channel that was opened byOSSL_STORE_open()and frees all other information that was stored in theOSSL_STORE_CTX, as well as theOSSL_STORE_CTXitself. if ctx isNULLit does nothing. graceful exit, no drama. π
π NOTES π
a string without a scheme prefix (that is, a non-URI string) is implicitly interpreted as using the file: scheme. sneaky but convenient. π
there are some tools that can be used together with OSSL_STORE_open() to determine if any failure is caused by an unparsable URI, or if it's a different error (such as memory allocation failures); if the URI was parsable but the scheme unregistered, the top error will have the reason "OSSL_STORE_R_UNREGISTERED_SCHEME". write that down. π
these functions make no direct assumption regarding the pass phrase received from the password callback. the loaders may make assumptions, however. for example, the file: scheme loader inherits the assumptions made by OpenSSL functionality that handles the different file types; this is mostly relevant for PKCS#12 objects. see passphrase-encoding(7) for further information. π₯
π RETURN VALUES π
OSSL_STORE_open()β returns a pointer to anOSSL_STORE_CTXon success, orNULLon failure.OSSL_STORE_load()β returns a pointer to anOSSL_STORE_INFOon success, orNULLon error or when end of data is reached. useOSSL_STORE_error()andOSSL_STORE_eof()to determine the meaning of a returnedNULL. don't just assume, bestie, go ask. πOSSL_STORE_eof()β returns1if the end of data has been reached or an error occurred,0otherwise.OSSL_STORE_error()β returns1if an error occurred in anOSSL_STORE_load()call, otherwise0.OSSL_STORE_delete(),OSSL_STORE_ctrl()andOSSL_STORE_close()β return1on success, or0on failure.
π¦ SEE ALSO π¦
ossl_store(7), OSSL_STORE_INFO(3), OSSL_STORE_register_loader(3), passphrase-encoding(7)
β HISTORY β
OSSL_STORE_delete()was added in OpenSSL 3.2.OSSL_STORE_open_ex()was added in OpenSSL 3.0.OSSL_STORE_CTX,OSSL_STORE_post_process_info_fn(),OSSL_STORE_open(),OSSL_STORE_ctrl(),OSSL_STORE_load(),OSSL_STORE_eof()andOSSL_STORE_close()were added in OpenSSL 1.1.1.- handling of
NULLctx argument forOSSL_STORE_close()was introduced in OpenSSL 1.1.1h. OSSL_STORE_ctrl()andOSSL_STORE_vctrl()were deprecated in OpenSSL 3.0.
π COPYRIGHT π
Copyright 2016-2023 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>.
and that's the whole page, bestie!! πβ¨ this was OpenSSL 3.5.9, dated 2026-09-29, and it's the OSSL_STORE_OPEN(3ossl) manual β go read some objects from a URI, you absolute legend. mwah. ππ¦πΈ
π¦ 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