Prevent crash with engine using different openssl runtime
authorBernd Edlinger <bernd.edlinger@hotmail.de>
Mon, 22 Nov 2021 20:50:04 +0000 (21:50 +0100)
committerBernd Edlinger <bernd.edlinger@hotmail.de>
Tue, 8 Feb 2022 12:28:24 +0000 (13:28 +0100)
commit01d4f5cdd4125bd81878257ae357ff191bc31dd1
tree7a179eb6e0e0e2a0a1fcf3d9574eeb01eec80603
parentd7975674e5aaded44a6845d3d1beac08477a22ad
Prevent crash with engine using different openssl runtime

This problem happens usually because an application
links libcrypto and/or libssl statically which
installs an atexit handler, but later an engine using
a shared instance of libcrypto is installed.
The problem is in simple words that both instances
of libcrypto have an atexit handler installed,
but both are unable to coordinate with each other,
which causes a crash, typically a use-after-free
in the engine's destroy function.

Work around that by preventing the engine's
libcrypto to install the atexit handler.
This may result in a small memory leak, but that
memory is still reachable.

Fixes #15898

Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/17112)

(cherry picked from commit 9362a1b32b7330e24d3bca230b412557caea095b)
include/openssl/engine.h