Things can get messy when application decides to use it's own memory
allocation functions using CRYPTO_set_mem_functions(3ossl)
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Paul Dale <ppzgs1@gmail.com>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/27163)
return 1;
OPENSSL_free(dgbl->random_provider_name);
- dgbl->random_provider_name = strdup(name);
+ dgbl->random_provider_name = OPENSSL_strdup(name);
return dgbl->random_provider_name != NULL;
}
ret = chdir(s);
if (ret == 0)
- new_config_name = strdup(last + DIRSEP_PRESERVE + 1);
+ new_config_name = OPENSSL_strdup(last + DIRSEP_PRESERVE + 1);
err:
OPENSSL_free(s);
return new_config_name;