]> git.ipfire.org Git - thirdparty/openssl.git/commit
Don't call OPENSSL_init_crypto from inside a RUN_ONCE
authorMatt Caswell <matt@openssl.org>
Fri, 31 Mar 2023 09:35:32 +0000 (10:35 +0100)
committerTomas Mraz <tomas@openssl.org>
Tue, 4 Apr 2023 07:36:42 +0000 (09:36 +0200)
commit540c2d175d3c7c28bb969a74f6fe0396f0addc1a
treeff68b6a856901292fbe0209093f95800d34ed07d
parent418c6c520764491262018c45481a20ef10cd3bca
Don't call OPENSSL_init_crypto from inside a RUN_ONCE

Calling OPENSSL_init_crypto from inside a RUN_ONCE seems like a bad idea.
This is especially bad if OPENSSL_init_crypto can recursively end up
attempting to call the RUN_ONCE that we're already inside.

The initialisation in OPENSSL_init_crypto is already "run once" protected.
There is no need to protect it "twice".

Fixes #20653

Reviewed-by: Paul Dale <pauli@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/20662)

(cherry picked from commit a9745427cd5d44a76b31690b4a2c6bef2ee677c4)
crypto/objects/obj_dat.c