Lines Matching full:provider

177 A provider in OpenSSL is a component that collects together algorithm
179 provider loaded that contains an implementation of it. OpenSSL comes with a
181 don't load a provider explicitly (either in program code or via config) then the
182 OpenSSL built-in \*(L"default\*(R" provider will be automatically loaded.
186 options take effect. When a provider is loaded, it is only loaded within the
240 \&\*(L"provider=default\*(R" could be used to force the selection to only consider
241 algorithm implementations in the default provider.
254 Users of the OpenSSL libraries never query a provider directly for an algorithm
271 no provider has been loaded in this library context then the default provider
308 Fetch the operation type implementation from any provider given a library
311 If the provider of the operation type implementation is different from the
312 provider of the \s-1\fBEVP_PKEY\s0\fR\|(3)'s \s-1\fBEVP_KEYMGMT\s0\fR\|(3) implementation, try to
313 fetch a \s-1\fBEVP_KEYMGMT\s0\fR\|(3) implementation in the same provider as the operation
320 provider as the original \s-1\fBEVP_PKEY\s0\fR\|(3)'s \s-1\fBEVP_KEYMGMT\s0\fR\|(3), still using the
333 internally fetch methods from a provider.
339 Fetching via a provider offers more flexibility, but it is slower than the
341 and then populate the method table using provider supplied methods.
402 Fetch an implementation of \s-1SHA2\-256\s0 from the default provider in the default
406 \& EVP_MD *md = EVP_MD_fetch(NULL, "SHA2\-256", "provider=default");
411 Fetch an implementation of \s-1SHA2\-256\s0 that is not from the default provider in the
415 \& EVP_MD *md = EVP_MD_fetch(NULL, "SHA2\-256", "provider!=default");
420 Fetch an implementation of \s-1SHA2\-256\s0 from the default provider in the specified
424 \& EVP_MD *md = EVP_MD_fetch(ctx, "SHA2\-256", "provider=default");
429 Load the legacy provider into the default context and then fetch an
436 \& EVP_MD *md = EVP_MD_fetch(NULL, "WHIRLPOOL", "provider=legacy");
441 Note that in the above example the property string \*(L"provider=legacy\*(R" is optional
443 the \*(L"whirlpool\*(R" algorithm is in the \*(L"legacy\*(R" provider. Also note that the
444 default provider should be explicitly loaded if it is required in addition to
467 algorithm identifier to the appropriate fetching function. Also see the provider
472 For information on writing a provider see \fBprovider\fR\|(7).
473 .SS "Default provider"
474 .IX Subsection "Default provider"
475 The default provider is built in as part of the \fIlibcrypto\fR library and
478 algorithms), the property query string \*(L"provider=default\*(R" can be used as a
479 search criterion for these implementations.  The default provider includes all
480 of the functionality in the base provider below.
482 If you don't load any providers at all then the \*(L"default\*(R" provider will be
483 automatically loaded. If you explicitly load any provider then the \*(L"default\*(R"
484 provider would also need to be explicitly loaded if it is required.
487 .SS "Base provider"
488 .IX Subsection "Base provider"
489 The base provider is built in as part of the \fIlibcrypto\fR library and contains
493 \&\*(L"provider=base\*(R" can be used as a search criterion for these implementations.
495 implementations in themselves but support algorithms from the \s-1FIPS\s0 provider and
500 .SS "\s-1FIPS\s0 provider"
501 .IX Subsection "FIPS provider"
502 The \s-1FIPS\s0 provider is a dynamically loadable module, and must therefore
507 property query string \*(L"provider=fips\*(R" can be used as a search criterion for
509 provider can also be selected with the property \*(L"fips=yes\*(R". The \s-1FIPS\s0 provider
514 .SS "Legacy provider"
515 .IX Subsection "Legacy provider"
516 The legacy provider is a dynamically loadable module, and must therefore
521 the property \*(L"provider=legacy\*(R" can be used as a search criterion for these
525 .SS "Null provider"
526 .IX Subsection "Null provider"
527 The null provider is built in as part of the \fIlibcrypto\fR library. It contains
528 no algorithms in it at all. When fetching algorithms the default provider will
529 be automatically loaded if no other provider has been explicitly loaded. To
530 prevent that from happening you can explicitly load the null provider.
646 provider. They are also duplicated in the base provider.
679 \&\fBopenssl\-glossary\fR\|(7), \fBprovider\fR\|(7)