Lines Matching full:provider

95 A provider in OpenSSL is a component that collects together algorithm
98 provider loaded that contains an implementation of it. OpenSSL comes with a
103 built-in provider is one that is either already present in \f(CW\*(C`libcrypto\*(C'\fR or one
107 If you don't load a provider explicitly (either in program code or via config)
108 then the OpenSSL built-in "default" provider will be automatically loaded.
120 a provider is loaded, it is only loaded within the scope of a given library
145 of any given algorithm might be available. For example the OpenSSL FIPS provider
147 available in the OpenSSL default provider.
152 string of "provider=default" could be used to force the selection to only
153 consider algorithm implementations in the default provider.
227 algorithm identifier to the appropriate fetching function. Also see the provider
232 For information on writing a provider see \fBprovider\fR\|(7).
233 .SS "Default provider"
234 .IX Subsection "Default provider"
235 The default provider is built-in as part of the \fIlibcrypto\fR library and
238 algorithms), the property query string "provider=default" can be used as a
239 search criterion for these implementations.  The default provider includes all
240 of the functionality in the base provider below.
242 If you don't load any providers at all then the "default" provider will be
243 automatically loaded. If you explicitly load any provider then the "default"
244 provider would also need to be explicitly loaded if it is required.
247 .SS "Base provider"
248 .IX Subsection "Base provider"
249 The base provider is built in as part of the \fIlibcrypto\fR library and contains
255 implementations in themselves but support algorithms from the FIPS provider and
260 .SS "FIPS provider"
261 .IX Subsection "FIPS provider"
262 The FIPS provider is a dynamically loadable module, and must therefore
267 property query string "provider=fips" can be used as a search criterion for
269 provider can also be selected with the property "fips=yes". The FIPS provider
273 Typically the "Base provider" will also need to be loaded because the FIPS
274 provider does not support the encoding or decoding of keys.
277 .SS "Legacy provider"
278 .IX Subsection "Legacy provider"
279 The legacy provider is a dynamically loadable module, and must therefore
284 the property "provider=legacy" can be used as a search criterion for these
288 .SS "Null provider"
289 .IX Subsection "Null provider"
290 The null provider is built in as part of the \fIlibcrypto\fR library. It contains
291 no algorithms in it at all. When fetching algorithms the default provider will
292 be automatically loaded if no other provider has been explicitly loaded. To
293 prevent that from happening you can explicitly load the null provider.
297 accidentally using the default library context. Load the null provider into the
364 \&\fBopenssl\-glossary\fR\|(7), \fBprovider\fR\|(7)