summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDmitry Belyavskiy <beldmit@gmail.com>2024-12-18 21:28:14 +0100
committerDmitry Belyavskiy <beldmit@gmail.com>2024-12-20 18:20:17 +0100
commitb3bb214720f20f3b126ae4b9c330e9a48b835415 (patch)
treea079d4bb58b116dfc0a339a34decb3ffb3f451cc
parentThis is a test for nocache provider behavior (diff)
downloadopenssl-b3bb214720f20f3b126ae4b9c330e9a48b835415.tar.xz
openssl-b3bb214720f20f3b126ae4b9c330e9a48b835415.zip
Take into account no_store when pushing algorithm
When we put algorithm to the store, we have a fallback to the OSSL_LIB_CTX level store when store is NULL. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/26197)
-rw-r--r--crypto/core_fetch.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/crypto/core_fetch.c b/crypto/core_fetch.c
index d311158d77..70715e7d6a 100644
--- a/crypto/core_fetch.c
+++ b/crypto/core_fetch.c
@@ -120,7 +120,7 @@ static void ossl_method_construct_this(OSSL_PROVIDER *provider,
* It is *expected* that the put function increments the refcnt
* of the passed method.
*/
- data->mcm->put(data->store, method, provider, algo->algorithm_names,
+ data->mcm->put(no_store ? data->store : NULL, method, provider, algo->algorithm_names,
algo->property_definition, data->mcm_data);
/* refcnt-- because we're dropping the reference */