OSSL_STORE_OPEN(3ossl)
π OSSL_STORE_OPEN π
okay so bestie, this is the 3ossl OpenSSL manual for the whole OSSL_STORE crew: the types and functions that read objects from a URI. Itβs giving βopen the URI, grab the objects, close the vibeβ and honestly itβs iconic π
β¨
π 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 π«Ά
β¨ 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);
β οΈ heads up bestie:OSSL_STORE_ctrl()has been deprecated since OpenSSL 3.0, and it can be hidden entirely by definingOPENSSL_API_COMPATwith a suitable version value β seeopenssl_user_macros(7)for the deets π
int OSSL_STORE_ctrl(OSSL_STORE_CTX *ctx, int cmd, ... /* args */);
πΈ DESCRIPTION πΈ
These functions help an app fetch supported objects from a given URI β and yes, the "SUPPORTED OBJECTS" section in OSSL_STORE_INFO(3) is where you find out which objects those are π The whole ritual is: βopenβ the URI with OSSL_STORE_open(), read each available and supported object with OSSL_STORE_load() as long as OSSL_STORE_eof() hasnβt been reached, then finish it off with OSSL_STORE_close() β¨
The retrieved information is stored in an OSSL_STORE_INFO, which is further described in OSSL_STORE_INFO(3) π¦
π§Έ Types π§Έ
OSSL_STORE_CTX is the 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.
π οΈ Functions π οΈ
OSSL_STORE_open_ex()β takes aurior pathuri, a password UI methodui_methodwith associated dataui_data, a post-processing callbackpost_processwith associated datapost_process_data, a library contextlibctxwith an associated property querypropq, and opens a channel to the data located at the URI. It returns aOSSL_STORE_CTXwith all necessary internal information. The givenui_methodandui_datawill be reused by all functions that useOSSL_STORE_CTXwhen interaction is needed, for instance to provide a password. The auxiliaryOSSL_PARAM(3)parameters inparamscan be set to further modify the store operation. The givenpost_processandpost_process_datawill be reused byOSSL_STORE_load()to manipulate or drop the value to be returned. Thepost_processfunction drops values by returningNULL, which will causeOSSL_STORE_load()to start its process over with loading the next object, untilpost_processreturns something other thanNULL, or the end of data is reached as indicated byOSSL_STORE_eof()πOSSL_STORE_open()β similar toOSSL_STORE_open_ex()but usesNULLfor theparams, the library contextlibctxand property querypropq.OSSL_STORE_ctrl()β takes aOSSL_STORE_CTX, and command numbercmdand 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.
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.OSSL_STORE_load()β takes aOSSL_STORE_CTXand tries to load the next available object and return it wrapped withOSSL_STORE_INFO.OSSL_STORE_delete()β deletes the object identified byuri.OSSL_STORE_eof()β takes aOSSL_STORE_CTXand checks if weβve reached the end of data.OSSL_STORE_error()β takes aOSSL_STORE_CTXand checks if an error occurred in the lastOSSL_STORE_load()call. Note that it may still be meaningful to try and load more objects, unlessOSSL_STORE_eof()shows that the end of data has been reached.OSSL_STORE_close()β takes aOSSL_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. IfctxisNULLit does nothing.
π¦ NOTES π¦
A string without a scheme prefix (that is, a non-URI string) is implicitly interpreted as using the file: scheme.
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" π
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 aOSSL_STORE_CTXon success, orNULLon failure.OSSL_STORE_load()returns a pointer to aOSSL_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.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 π«Ά
π 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
NULLctxargument 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>.
mwah π thatβs the whole page, bestie β OpenSSL 3.5.6, dated 2026-04-07. go read some objects from a URI, periodt π«Άβ¨
π¦ 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