Lines Matching full:provider

148 \&\- provider routines
152 \& #include <openssl/provider.h>
165 \&                          int (*cb)(OSSL_PROVIDER *provider, void *cbdata),
194 implementation providers (see \fBprovider\fR\|(7) for information on what a
195 provider is).
196 A provider can be built in to the application or the OpenSSL
209 \&\fBOSSL_PROVIDER_add_builtin()\fR is used to add a built in provider to
211 provider name with a provider initialization function.
214 \&\fBOSSL_PROVIDER_load()\fR loads and initializes a provider.
215 This may simply initialize a provider that was previously added with
217 or load a provider module with the given name and run its provider
219 to a provider module, in that case the provider name as returned
226 it does not disable the fallback providers if the provider cannot be
228 If the provider loads successfully and \fIretain_fallbacks\fR is zero, the
231 \&\fBOSSL_PROVIDER_unload()\fR unloads the given provider.
232 For a provider added with \fBOSSL_PROVIDER_add_builtin()\fR, this simply
235 \&\fBOSSL_PROVIDER_available()\fR checks if a named provider is available
239 \&\fIcb\fR for each one, with the current provider in \fIprovider\fR and the
240 \&\fIcbdata\fR that comes from the caller. If no other provider has been loaded
241 before calling this function, the default provider is still available as
246 \&\fBOSSL_PROVIDER_gettable_params()\fR is used to get a provider parameter
249 \&\fBOSSL_PROVIDER_get_params()\fR is used to get provider parameter values.
254 \&\fBOSSL_PROVIDER_self_test()\fR is used to run a provider's self tests on demand.
255 If the self tests fail then the provider will fail to provide any further
259 \&\fBOSSL_PROVIDER_query_operation()\fR calls the provider's \fIquery_operation\fR
260 function (see \fBprovider\fR\|(7)), if the provider has one. It returns an
265 \&\fBOSSL_PROVIDER_unquery_operation()\fR calls the provider's \fIunquery_operation\fR
266 function (see \fBprovider\fR\|(7)), if the provider has one.  This is considered a
269 \&\fBOSSL_PROVIDER_get0_provider_ctx()\fR returns the provider context for the given
270 provider. The provider context is an opaque handle set by the provider itself
271 and is passed back to the provider by libcrypto in various function calls.
273 \&\fBOSSL_PROVIDER_get0_dispatch()\fR returns the provider's dispatch table as it was
274 returned in the \fIout\fR parameter from the provider's init function. See
281 \&\fBOSSL_PROVIDER_get0_name()\fR returns the name of the given provider.
284 supported by the provider specified in \fIprov\fR with the capability name
285 \&\fIcapability\fR. For each capability of that name supported by the provider it
289 \&\*(L"\s-1CAPABILTIIES\*(R"\s0 in \fBprovider\-base\fR\|(7).
297 provider object on success, or \s-1NULL\s0 on error.
300 provider it is called with, or 0 if any provider callback invocation returns 0;
301 callback processing stops at the first callback invocation on a provider
304 \&\fBOSSL_PROVIDER_available()\fR returns 1 if the named provider is available,
318 This demonstrates how to load the provider module \*(L"foo\*(R" and ask for
323 \& #include <openssl/provider.h>
335 \&     printf("Provider \*(Aqfoo\*(Aq buildinfo: %s\en", build);
341 \&\fBopenssl\-core.h\fR\|(7), \s-1\fBOSSL_LIB_CTX\s0\fR\|(3), \fBprovider\fR\|(7)