Fix statically linked engine initialization w/ fips
authorMatt Hauck <matt.hauck@tanium.com>
Wed, 13 Jul 2016 18:27:40 +0000 (11:27 -0700)
committerRichard Levitte <levitte@openssl.org>
Thu, 9 Feb 2017 22:39:40 +0000 (23:39 +0100)
commit28903862fb0d6351dd88522950375ed44c10d1ba
tree880d15c8436366a25150e8793fb9bb46aef30325
parent348681ff2b30453eb03ce2d83022ef069d86877d
Fix statically linked engine initialization w/ fips

This only manifested itself with FIPS enabled statically linked
engines. The OPENSSL_init call ended up invoking RAND_init_fips
for a FIPS enabled build, which called CRYPTO_malloc, resulting in
disallowing the engine to finish its IMPLEMENT_DYNAMIC_BIND_FN call.

(Merged from https://github.com/openssl/openssl/pull/1308)Reviewed-by: Geoff Thorpe <geoff@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
CLA: trivial
(Merged from https://github.com/openssl/openssl/pull/1308)
crypto/mem.c