Lines Matching +full:in +full:- +full:application

8 OPENSSL_thread_stop_ex, OPENSSL_thread_stop - OpenSSL initialisation
35 application is multi-threaded), and these resources must be freed prior to the
49 Therefore, in order to perform nondefault initialisation,
50 OPENSSL_init_crypto() MUST be called by application code prior to
105 Note that in OpenSSL 1.1.1 this was the default for libssl but not for
108 In OpenSSL 1.1.0 this was a nondefault option for both libssl and libcrypto.
120 sub-library (see L<ASYNC_start_job(3)>). This is a default option.
126 in OpenSSL 3.0.
132 in OpenSSL 3.0.
138 in OpenSSL 3.0.
144 in OpenSSL 3.0.
150 in OpenSSL 3.0.
156 in OpenSSL 3.0.
162 in OpenSSL 3.0.
167 built in engines listed above with the exception of the openssl and afalg
169 in OpenSSL 3.0.
180 the application will have to clean up OpenSSL explicitly using
185 Multiple options may be combined together in a single call to
194 automatically on application exit. This is done via the standard C library
195 atexit() function. In the event that the application will close in a manner
196 that will not call the registered atexit() handlers then the application should
199 on auto-deinitialisation. This is to avoid error conditions where both an
200 application and a library it depends on both use OpenSSL, and the library
201 deinitialises it before the application has finished using it.
207 be put through the openssl errstr command line application to produce a human
208 readable error (see L<openssl-errstr(1)>).
213 process wide resources are freed. In the event that multiple stop handlers are
218 can be NULL in which case the default OSSL_LIB_CTX is used.
230 should be freed before library exit, or under the circumstances described in
237 L<CONF_modules_load_file(3)> with NULL filename and application name and the
240 The filename, application name, and flags can be customized by providing a
241 non-null B<OPENSSL_INIT_SETTINGS> object.
246 nondefault application name.
248 If the B<CONF_MFLAGS_IGNORE_RETURN_CODES> flag is not included, any errors in
257 (e.g. in a pthreads environment, when pthread_exit() is called). On Windows
258 platforms this is done in response to a DLL_THREAD_DETACH message being sent to
260 without sending this message (for example ExitProcess()). If the application
261 uses such functions, then the application must free up OpenSSL resources
269 On Linux/Unix where OpenSSL has been loaded via dlopen() and the application is
270 multi-threaded and if dlclose() is subsequently called prior to the threads
272 with those threads. The application should either call OPENSSL_thread_stop() on
289 and OPENSSL_INIT_free() functions were added in OpenSSL 1.1.0.
293 Copyright 2016-2024 The OpenSSL Project Authors. All Rights Reserved.
296 this file except in compliance with the License.  You can obtain a copy
297 in the file LICENSE in the source distribution or at