OSSL_PROVIDER(3ossl)
π OSSL_PROVIDER(3ossl) π
okay bestie, welcome to the OSSL_PROVIDER(3ossl) page β it's giving OpenSSL provider routines, and it's literally the whole backstage pass to how providers work. No cap, this one is long, so part 1 is right here, part 2 is coming. π
β¨ NAME β¨
okay so this page is all about the provider routines: OSSL_PROVIDER_set_default_search_path, OSSL_PROVIDER_get0_default_search_path, OSSL_PROVIDER, OSSL_PROVIDER_load, OSSL_PROVIDER_try_load, OSSL_PROVIDER_unload, OSSL_PROVIDER_load_ex, OSSL_PROVIDER_try_load_ex, OSSL_PROVIDER_available, OSSL_PROVIDER_do_all, OSSL_PROVIDER_gettable_params, OSSL_PROVIDER_get_params, OSSL_PROVIDER_query_operation, OSSL_PROVIDER_unquery_operation, OSSL_PROVIDER_get0_provider_ctx, OSSL_PROVIDER_get0_dispatch, OSSL_PROVIDER_add_builtin, OSSL_PROVIDER_get0_name, OSSL_PROVIDER_get_capabilities, OSSL_PROVIDER_add_conf_parameter, OSSL_PROVIDER_get_conf_parameters, OSSL_PROVIDER_conf_get_bool, OSSL_PROVIDER_self_test β provider routines. π
πΈ SYNOPSIS πΈ
okay so here's the exact tea, bestie:
#include <openssl/provider.h>
typedef struct ossl_provider_st OSSL_PROVIDER;
int OSSL_PROVIDER_set_default_search_path(OSSL_LIB_CTX *libctx,
const char *path);
const char *OSSL_PROVIDER_get0_default_search_path(OSSL_LIB_CTX *libctx);
OSSL_PROVIDER *OSSL_PROVIDER_load(OSSL_LIB_CTX *libctx, const char *name);
OSSL_PROVIDER *OSSL_PROVIDER_load_ex(OSSL_LIB_CTX *, const char *name,
OSSL_PARAM *params);
OSSL_PROVIDER *OSSL_PROVIDER_try_load(OSSL_LIB_CTX *libctx, const char *name,
int retain_fallbacks);
OSSL_PROVIDER *OSSL_PROVIDER_try_load_ex(OSSL_LIB_CTX *, const char *name,
OSSL_PARAM *params,
int retain_fallbacks);
int OSSL_PROVIDER_unload(OSSL_PROVIDER *prov);
int OSSL_PROVIDER_available(OSSL_LIB_CTX *libctx, const char *name);
int OSSL_PROVIDER_do_all(OSSL_LIB_CTX *ctx,
int (*cb)(OSSL_PROVIDER *provider, void *cbdata),
void *cbdata);
const OSSL_PARAM *OSSL_PROVIDER_gettable_params(OSSL_PROVIDER *prov);
int OSSL_PROVIDER_get_params(OSSL_PROVIDER *prov, OSSL_PARAM params[]);
const OSSL_ALGORITHM *OSSL_PROVIDER_query_operation(const OSSL_PROVIDER *prov,
int operation_id,
int *no_cache);
void OSSL_PROVIDER_unquery_operation(const OSSL_PROVIDER *prov,
int operation_id,
const OSSL_ALGORITHM *algs);
void *OSSL_PROVIDER_get0_provider_ctx(const OSSL_PROVIDER *prov);
const OSSL_DISPATCH *OSSL_PROVIDER_get0_dispatch(const OSSL_PROVIDER *prov);
int OSSL_PROVIDER_add_builtin(OSSL_LIB_CTX *libctx, const char *name,
ossl_provider_init_fn *init_fn);
const char *OSSL_PROVIDER_get0_name(const OSSL_PROVIDER *prov);
int OSSL_PROVIDER_get_capabilities(const OSSL_PROVIDER *prov,
const char *capability,
OSSL_CALLBACK *cb,
void *arg);
int OSSL_PROVIDER_add_conf_parameter(OSSL_PROVIDER *prov, const char *name,
const char *value);
int OSSL_PROVIDER_get_conf_parameters(OSSL_PROVIDER *prov,
OSSL_PARAM params[]);
int OSSL_PROVIDER_conf_get_bool(const OSSL_PROVIDER *prov,
const char *name, int defval);
int OSSL_PROVIDER_self_test(const OSSL_PROVIDER *prov);
π DESCRIPTION π
OSSL_PROVIDER is a type that holds internal information about implementation providers β peep provider(7) for info on what a provider even is. A provider can be built in to the application or the OpenSSL libraries, or it can be a loadable module. The functions described here handle both forms. π
Some of these functions operate within a library context, so please see OSSL_LIB_CTX(3) for further details.
β¨ Functions β¨
OSSL_PROVIDER_set_default_search_path()β specifies the default search path that is to be used for looking for providers in the specifiedlibctx. If left unspecified, an environment variable and a fall back default value will be used instead.OSSL_PROVIDER_get0_default_search_path()β retrieves the default search path that is to be used for looking for providers in the specifiedlibctx. If successful, returns the path or empty string; the path is valid until the context is released orOSSL_PROVIDER_set_default_search_path()is called.OSSL_PROVIDER_add_builtin()β adds a built in provider to theOSSL_PROVIDERstore in the given library context, by associating a provider name with a provider initialization function. This name can then be used withOSSL_PROVIDER_load().OSSL_PROVIDER_load()β loads and initializes a provider. This may simply initialize a provider that was previously added withOSSL_PROVIDER_add_builtin()and run its given initialization function, or load a provider module with the given name and run its provider entry point,"OSSL_provider_init". The name can be a path to a provider module, in that case the provider name as returned byOSSL_PROVIDER_get0_name()will be the path. Interpretation of relative paths is platform dependent and they are relative to the configured"MODULESDIR"directory or the path set in the environment variableOPENSSL_MODULESif set.OSSL_PROVIDER_try_load()β functions likeOSSL_PROVIDER_load(), except that it does not disable the fallback providers if the provider cannot be loaded and initialized or ifretain_fallbacksis nonzero. If the provider loads successfully andretain_fallbacksis zero, the fallback providers are disabled.OSSL_PROVIDER_load_ex()andOSSL_PROVIDER_try_load_ex()β are the variants of the previous functions accepting an"OSSL_PARAM"array of the parameters that are passed as the configuration of the loaded provider. The parameters of any type but"OSSL_PARAM_UTF8_STRING"are silently ignored. If the parameters are provided, they replace all the ones specified in the configuration file.OSSL_PROVIDER_unload()β unloads the given provider. For a provider added withOSSL_PROVIDER_add_builtin(), this simply runs its teardown function.OSSL_PROVIDER_available()β checks if a named provider is available for use.OSSL_PROVIDER_do_all()β iterates over all loaded providers, callingcbfor each one, with the current provider inproviderand thecbdatathat comes from the caller. If no other provider has been loaded before calling this function, the default provider is still available as fallback. SeeOSSL_PROVIDER-default(7)for more information on this fallback behaviour.OSSL_PROVIDER_gettable_params()β is used to get a provider parameter descriptor set as a constantOSSL_PARAM(3)array.OSSL_PROVIDER_get_params()β is used to get provider parameter values. The caller must prepare theOSSL_PARAM(3)array before calling this function, and the variables acting as buffers for this parameter array should be filled with data when it returns successfully.OSSL_PROVIDER_add_conf_parameter()β sets the provider configuration parameternametovalue. Provider configuration parameters are managed by the OpenSSL core and normally set in the configuration file, but can also be set early in the main program before a provider is in use by multiple threads. Parameters that only affect provider initialisation must, for now, be set in the configuration file, only parameters that are also queried later have any affect when set via this interface. Only text parameters can be given, and it's up to the provider to interpret them.OSSL_PROVIDER_get_conf_parameters()β retrieves global configuration parameters associated withprov. These configuration parameters are stored for each provider by the OpenSSL core, not the provider itself, parameters managed by the provider are queried viaOSSL_PROVIDER_get_params()described above. The parameters are returned by reference, not as copies, and so the elements of theparamarray must haveOSSL_PARAM_UTF8_PTRas their data_type.OSSL_PROVIDER_conf_get_bool()β parses the global configuration parameternameassociated with providerprovas a boolean value, returning a default valuedefvalwhen unable to retrieve or parse the parameter. Parameter values equal (case-insensitively) to1,"on","yes", or"true"yield a true (nonzero) result. Parameter values equal (case-insensitively) to0,"off","no", or"false"yield a false (zero) result.OSSL_PROVIDER_self_test()β is used to run a provider's self tests on demand. If the self tests fail then the provider will fail to provide any further services and algorithms.OSSL_SELF_TEST_set_callback(3)may be called beforehand in order to display diagnostics for the running self tests.OSSL_PROVIDER_query_operation()β calls the provider'squery_operationfunction (seeprovider(7)), if the provider has one. It returns an array ofOSSL_ALGORITHMfor the givenoperation_idterminated by an all NULLOSSL_ALGORITHMentry. This is considered a low-level function that most applications should not need to call.OSSL_PROVIDER_unquery_operation()β calls the provider'sunquery_operationfunction (seeprovider(7)), if the provider has one. This is considered a low-level function that most applications should not need to call.OSSL_PROVIDER_get0_provider_ctx()β returns the provider context for the given provider. The provider context is an opaque handle set by the provider itself and is passed back to the provider by libcrypto in various function calls.OSSL_PROVIDER_get0_dispatch()β returns the provider's dispatch table as it was returned in the out parameter from the provider's init function. Seeprovider-base(7).
If it is permissible to cache references to this array then *no_store is set to 0 or 1 otherwise. If the array is not cacheable then it is assumed to have a short lifetime.
OSSL_PROVIDER_get0_name()β returns the name of the given provider.OSSL_PROVIDER_get_capabilities()β provides information about the capabilities supported by the provider specified inprovwith the capability namecapability. For each capability of that name supported by the provider it will call the callbackcband supply a set ofOSSL_PARAM(3)s describing the capability. It will also pass back the argumentarg. For more details about capabilities and what they can be used for please see"CAPABILITIES"inprovider-base(7).
π RETURN VALUES π
okay bestie, here's the receipts on what each function hands back to you β¨
OSSL_PROVIDER_set_default_search_path(),OSSL_PROVIDER_add(),OSSL_PROVIDER_unload(),OSSL_PROVIDER_get_params(),OSSL_PROVIDER_add_conf_parameter(),OSSL_PROVIDER_get_conf_parameters()andOSSL_PROVIDER_get_capabilities()β these all give you 1 when it works and 0 when it doesn't. that's it, that's the whole personality πOSSL_PROVIDER_get0_default_search_path()β hands you a pointer to a path if it goes well, or NULL if something errored or if that path was never set in the first place. no path, no pointer, periodt πOSSL_PROVIDER_load()andOSSL_PROVIDER_try_load()β you get a pointer to a provider object when it works, NULL when it doesn't. iconic when it works, devastating when it's NULL πOSSL_PROVIDER_do_all()β returns 1 if your callbackcbreturns 1 for every provider it gets called with. returns 0 if any single provider callback invocation returns 0. and listen, the callback processing stops right at that first invocation that returns 0 β no second chances, no encore, it's done πΈOSSL_PROVIDER_available()β 1 if the named provider is available, otherwise 0. vibe check: passed or not passed, no in-between β¨OSSL_PROVIDER_gettable_params()β gives you a pointer to an array of constantOSSL_PARAM(3), or NULL if there isn't one provided. if it's not there, it's just not there, we don't make things up π¦OSSL_PROVIDER_get_params()β 1 on success, 0 on error. lowkey the most reliable girl in the friend group πOSSL_PROVIDER_query_operation()β returns an array ofOSSL_ALGORITHM, or NULL on error. arrays are giving main character energy fr fr πOSSL_PROVIDER_self_test()β 1 if the self tests pass, or 0 on error. it either aced the quiz or it didn't, no partial credit π
π EXAMPLES π
okay so this lil demo shows you how to load the provider module "foo" and then ask it for its build information. we love a nosy queen asking questions π
#include <openssl/params.h>
#include <openssl/provider.h>
#include <openssl/err.h>
OSSL_PROVIDER *prov = NULL;
const char *build = NULL;
OSSL_PARAM request[] = {
{ "buildinfo", OSSL_PARAM_UTF8_PTR, &build, 0, 0 },
{ NULL, 0, NULL, 0, 0 }
};
if ((prov = OSSL_PROVIDER_load(NULL, "foo")) != NULL
&& OSSL_PROVIDER_get_params(prov, request))
printf("Provider 'foo' buildinfo: %s\n", build);
else
ERR_print_errors_fp(stderr);
so real talk: if the load works and OSSL_PROVIDER_get_params() works, you print the buildinfo like a boss β¨ otherwise you dump the errors to stderr and we all have a little cry about it π
π SEE ALSO π
go read those too bestie, the lore is deep π«Ά
π HISTORY π
the type and functions described here? added in OpenSSL 3.0. so they're not new new, they're established π
OSSL_PROVIDER_load_ex and OSSL_PROVIDER_try_load_ex showed up later, in OpenSSL 3.2 β a lil glow-up moment β¨
and OSSL_PROVIDER_add_conf_parameter, OSSL_PROVIDER_get_conf_parameters, and OSSL_PROVIDER_conf_get_bool are the freshest of the fresh, added in OpenSSL 3.5 πΈ
π COPYRIGHT π
Copyright 2019-2025 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>.
ngl bestie, "you may not use this file except in compliance with the License" is the legal version of "read the group chat rules before you post" π
and that's a wrap on OSSL_PROVIDER(3ossl) π this whole page is from OpenSSL 3.5.9, dated 2026-09-29 β screenshot it, bookmark it, send it to the group chat, because that's the version that ate and left no crumbs β¨π
π
π¦ 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