Lines Matching +full:has +full:- +full:legacy +full:- +full:mode

1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-LIBRARIES-INTRODUCTION 7ossl"
58 .TH OSSL-GUIDE-LIBRARIES-INTRODUCTION 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-libraries\-introduction
65 \&\- OpenSSL Guide: An introduction to the OpenSSL libraries
101 Providers may either be "built-in" or in the form of a separate loadable module
103 built-in provider is one that is either already present in \f(CW\*(C`libcrypto\*(C'\fR or one
104 that the application has supplied itself directly. Third parties can also supply
108 then the OpenSSL built-in "default" provider will be automatically loaded.
138 automatically destroyed. No explicit de-initialisation steps need to be taken.
141 See also "ALGORITHM FETCHING" in \fBossl\-guide\-libcrypto\-introduction\fR\|(7).
163 See "ALGORITHM FETCHING" in \fBossl\-guide\-libcrypto\-introduction\fR\|(7) for more
166 .SH "MULTI-THREADED APPLICATIONS"
167 .IX Header "MULTI-THREADED APPLICATIONS"
168 As long as OpenSSL has been built with support for threads (the default case
169 on most platforms) then most OpenSSL \fIfunctions\fR are thread-safe in the sense
171 time. However most OpenSSL \fIdata structures\fR are not thread-safe. For example
183 See \fBopenssl\-threads\fR\|(7) for a more detailed discussion on OpenSSL threading
188 function has been successful or not. It is considered best practice to always
223 configuration options. The \fBopenssl\-list\fR\|(1) command can be used to list the
226 The names of the algorithms shown from \fBopenssl\-list\fR\|(1) can be used as an
235 The default provider is built-in as part of the \fIlibcrypto\fR library and
246 See \fBOSSL_PROVIDER\-default\fR\|(7).
256 are allowed for use in "FIPS mode". The property query string "fips=yes" can be
259 See \fBOSSL_PROVIDER\-base\fR\|(7).
270 may also contain non-approved algorithm implementations and these can be
276 See \fBOSSL_PROVIDER\-FIPS\fR\|(7) and \fBfips_module\fR\|(7).
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
287 See \fBOSSL_PROVIDER\-legacy\fR\|(7).
292 be automatically loaded if no other provider has been explicitly loaded. To
298 default library context so that the default library context has no algorithm
301 See \fBOSSL_PROVIDER\-null\fR\|(7).
350 \&\fBdemos\fR sub-directory.
356 See \fBossl\-guide\-libcrypto\-introduction\fR\|(7) for a more detailed introduction to
357 using \f(CW\*(C`libcrypto\*(C'\fR and \fBossl\-guide\-libssl\-introduction\fR\|(7) for more informa…
361 \&\fBopenssl\fR\|(1), \fBssl\fR\|(7), \fBevp\fR\|(7), \fBOSSL_LIB_CTX\fR\|(3), \fBopenssl\-threads\…
362 \&\fBproperty\fR\|(7), \fBOSSL_PROVIDER\-default\fR\|(7), \fBOSSL_PROVIDER\-base\fR\|(7),
363 \&\fBOSSL_PROVIDER\-FIPS\fR\|(7), \fBOSSL_PROVIDER\-legacy\fR\|(7), \fBOSSL_PROVIDER\-null\fR\|(7),
364 \&\fBopenssl\-glossary\fR\|(7), \fBprovider\fR\|(7)
367 Copyright 2000\-2023 The OpenSSL Project Authors. All Rights Reserved.