Lines Matching +full:activate +full:- +full:to +full:- +full:activate

4  - [Standard Providers](#standard-providers)
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)
10  - [Loading Providers](#loading-providers)
18 providers distributed with OpenSSL. In the future we expect third parties to
19 distribute their own providers which can be added to OpenSSL dynamically.
26 --------------------
28 The default provider collects together all of the standard built-in OpenSSL
31 that will be used. It is loaded automatically the first time that we try to
34 automatically. Therefore if you want to use it in conjunction with other
37 This is a "built-in" provider which means that it is compiled and linked
41 -------------------
45 However, some applications may need to use these algorithms for backwards
55 -----------------
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.
66 -----------------
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
70 serialize and deserialize keys to files. If you do not load the default
75 -----------------
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
81 This can be useful if you are using non-default library contexts and want
82 to ensure that the default library context is never used unintentionally.
87 Providers to be loaded can be specified in the OpenSSL config file.
88 See the [config(5)] manual page for information about how to configure
89 providers via the config file, and how to automatically activate them.
93 The following is a minimal config file example to load and activate both
106     activate = 1
109     activate = 1
111 It is also possible to load providers programmatically. For example you can
115 often also want to explicitly load the default provider, as is done here:
130             printf("Failed to load Legacy provider\n");
135             printf("Failed to load Default provider\n");