Lines Matching refs:provider

5     - [The Default Provider](#the-default-provider)
6     - [The Legacy Provider](#the-legacy-provider)
7     - [The FIPS Provider](#the-fips-provider)
8     - [The Base Provider](#the-base-provider)
9     - [The Null Provider](#the-null-provider)
16 algorithm is used via the high level APIs a provider is selected. It is that
17 provider implementation that actually does the required work. There are five
20 Documentation about writing providers is available on the [provider(7)]
23  [provider(7)]: https://www.openssl.org/docs/man3.0/man7/provider.html
28 The default provider collects together all of the standard built-in OpenSSL
30 explicitly (e.g. in the application or via config), then this is the provider
32 get an algorithm from a provider if no other provider has been loaded yet.
33 If another provider has already been loaded then it won't be loaded
37 This is a "built-in" provider which means that it is compiled and linked
43 The legacy provider is a collection of legacy algorithms that are either no
46 compatibility reasons. This provider is **not** loaded by default.
49 legacy provider explicitly.
51 Algorithms in the legacy provider include MD2, MD4, MDC2, RMD160, CAST5,
57 The FIPS provider contains a sub-set of the algorithm implementations available
58 from the default provider, consisting of algorithms conforming to FIPS standards.
59 It is intended that this provider will be FIPS140-2 validated.
62 implementations in this provider compared to the equivalent algorithm in the
63 default provider. This is typically in order to conform to FIPS standards.
68 The base provider contains a small sub-set of non-cryptographic algorithms
69 available in the default provider. For example, it contains algorithms to
71 provider then you should always load this one instead (in particular, if
72 you are using the FIPS provider).
77 The null provider is "built-in" to libcrypto and contains no algorithm
78 implementations. In order to guarantee that the default provider is not
79 automatically loaded, the null provider can be loaded instead.
94 the legacy and the default provider in the default library context.
112 load the legacy provider into the default library context as shown below.
113 Note that once you have explicitly loaded a provider into the library context
114 the default provider will no longer be automatically loaded. Therefore you will
115 often also want to explicitly load the default provider, as is done here:
120     #include <openssl/provider.h>
130             printf("Failed to load Legacy provider\n");
135             printf("Failed to load Default provider\n");