diff options
author | Matt Caswell <matt@openssl.org> | 2018-11-16 14:05:14 +0000 |
---|---|---|
committer | Matt Caswell <matt@openssl.org> | 2019-01-04 20:23:16 +0000 |
commit | 6b97cc6ec17586ff9c1d96ab5c3e0b6d829074a8 (patch) | |
tree | e591f6a1443069c45c5ecf22e9b0794025e0f974 /INSTALL | |
parent | f5f3dfd5efcc1e4073719f788ed4c40f8dc8cf3b (diff) |
Introduce a no-pinshared option
This option prevents OpenSSL from pinning itself in memory.
Fixes #7598
[extended tests]
Reviewed-by: Tim Hudson <tjh@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/7983)
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 18 |
1 files changed, 18 insertions, 0 deletions
@@ -407,6 +407,24 @@ no-pic Don't build with support for Position Independent Code. + no-pinshared By default OpenSSL will attempt to stay in memory until the + process exits. This is so that libcrypto and libssl can be + properly cleaned up automatically via an "atexit()" handler. + The handler is registered by libcrypto and cleans up both + libraries. On some platforms the atexit() handler will run on + unload of libcrypto (if it has been dynamically loaded) + rather than at process exit. This option can be used to stop + OpenSSL from attempting to stay in memory until the process + exits. This could lead to crashes if either libcrypto or + libssl have already been unloaded at the point + that the atexit handler is invoked, e.g. on a platform which + calls atexit() on unload of the library, and libssl is + unloaded before libcrypto then a crash is likely to happen. + Applications can suppress running of the atexit() handler at + run time by using the OPENSSL_INIT_NO_ATEXIT option to + OPENSSL_init_crypto(). See the man page for it for further + details. + no-posix-io Don't use POSIX IO capabilities. |