OSSL_PROVIDER(3ossl)
β¨ NAME β¨
okay bestie, welcome to the OSSL_PROVIDER(3ossl) provider-routines page β and yes, it is a whole lot of provider functions. This page covers 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, and OSSL_PROVIDER_self_test β provider routines, periodt. π«Ά
πΈ SYNOPSIS πΈ
include this and you're in, 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 β see provider(7) for the whole tea on what a provider actually 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, no cap. π
Some of these functions operate within a library context, so please peek at 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 specified libctx. 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 specified libctx. 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()β used to add a built in provider toOSSL_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 if retain_fallbacks is nonzero. If the provider loads successfully and retain_fallbacks is 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, calling cb for each one, with the current provider in provider and the cbdata that 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 parameter name to value. 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 with prov. 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 the param array must haveOSSL_PARAM_UTF8_PTRas their data_type.OSSL_PROVIDER_conf_get_bool()β parses the global configuration parameter name associated with provider prov as a boolean value, returning a default value defval when 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's query_operation function (seeprovider(7)), if the provider has one. It returns an array ofOSSL_ALGORITHMfor the given operation_id terminated 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's unquery_operation function (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).
tiny but important vibe check: if it is permissible to cache references to this array then*no_storeis set to0or1otherwise. 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 in prov with the capability name capability. For each capability of that name supported by the provider it will call the callback cb and supply a set ofOSSL_PARAM(3)s describing the capability. It will also pass back the argument arg. 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 vibe check on what everything 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 slay and return1on success, or0on error. that's the whole story π«ΆOSSL_PROVIDER_get0_default_search_path()β returns a pointer to a path when it works, orNULLon error, or if that path was never set in the first place. no path, no pointer, no drama πOSSL_PROVIDER_load()andOSSL_PROVIDER_try_load()β return a pointer to a provider object on success, orNULLon error. iconic behaviour fr fr βOSSL_PROVIDER_do_all()β returns1if the callbackcbreturns1for every provider it gets called with, or0if any single provider callback invocation returns0. and the second one happens, the callback processing stops right there at that first0. like, it does not keep going, it's done πOSSL_PROVIDER_available()β returns1if the named provider is available, otherwise0. simple as that πΈOSSL_PROVIDER_gettable_params()β returns a pointer to an array of constantOSSL_PARAM(3), orNULLif none is provided. if there's nothing to show you, you get nothing, respectfully πOSSL_PROVIDER_get_params()β returns1on success, or0on error. πOSSL_PROVIDER_query_operation()β returns an array ofOSSL_ALGORITHM, orNULLon error. π₯OSSL_PROVIDER_self_test()β returns1if the self tests pass, or0on error. the self tests are the vibe check for the provider itself, lowkey π
π EXAMPLES π
this one's a little demo of loading the provider module "foo" and asking it for its build information. watch and learn bestie, it's giving tutorial energy β¨
#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);
okay so real talk β if the load works and the params come back, you get your lil printf. otherwise the else branch hits and ERR_print_errors_fp(stderr) dumps the errors to stderr. no silent failures here, we don't do that π«Ά
π SEE ALSO π
openssl-core.h(7), OSSL_LIB_CTX(3), provider(7) β go read these next, they're literally the whole friend group of this page π
π« HISTORY π«
- the type and functions described here? added in OpenSSL 3.0 β
OSSL_PROVIDER_load_exandOSSL_PROVIDER_try_load_ex? those came in OpenSSL 3.2 β¨OSSL_PROVIDER_add_conf_parameter,OSSL_PROVIDER_get_conf_parameters, andOSSL_PROVIDER_conf_get_bool? newest of the bunch, 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>.
ok so the license thing isn't a suggestion, it's the whole rules-of-the-house situation. use it as the License says or don't use it at all, bestie π
and that's a wrap on this absolute icon of a manpage π this edition is OpenSSL 3.5.6, dated 2026-04-07 β go forth and load those providers, you've got this ππΈβ¨
π¦ 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