Lines Matching +full:application +full:- +full:notes

8 OPENSSL_thread_stop_ex, OPENSSL_thread_stop - OpenSSL initialisation
35 application is multi-threaded), and these resources must be freed prior to the
50 OPENSSL_init_crypto() MUST be called by application code prior to
120 sub-library (see L<ASYNC_start_job(3)>). This is a default option.
180 the application will have to clean up OpenSSL explicitly using
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)>).
231 the NOTES section below.
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.
254 =head1 NOTES  chapter
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
293 Copyright 2016-2024 The OpenSSL Project Authors. All Rights Reserved.