diff options
Diffstat (limited to 'doc/man7/provider-base.pod')
| -rw-r--r-- | doc/man7/provider-base.pod | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/man7/provider-base.pod b/doc/man7/provider-base.pod index 977f8566fe..a1822b916a 100644 --- a/doc/man7/provider-base.pod +++ b/doc/man7/provider-base.pod @@ -265,7 +265,6 @@ It will treat as success the case where the OID already exists (even if the short name I<sn> or long name I<ln> provided as arguments differ from those associated with the existing OID, in which case the new names are not associated). -This function is not thread safe. The core_obj_add_sigid() function registers a new composite signature algorithm (I<sign_name>) consisting of an underlying signature algorithm (I<pkey_name>) @@ -280,7 +279,6 @@ signature algorithm already exists (even if registered against a different underlying signature or digest algorithm). For I<digest_name>, NULL or an empty string is permissible for signature algorithms that do not need a digest to operate correctly. The function returns 1 on success or 0 on failure. -This function is not thread safe. CRYPTO_malloc(), CRYPTO_zalloc(), CRYPTO_free(), CRYPTO_clear_free(), CRYPTO_realloc(), CRYPTO_clear_realloc(), CRYPTO_secure_malloc(), @@ -609,6 +607,11 @@ or maximum. A -1 indicates that the group should not be used in that protocol. =back +=head1 NOTES + +The core_obj_create() and core_obj_add_sigid() functions were not thread safe +in OpenSSL 3.0. + =head1 EXAMPLES This is an example of a simple provider made available as a |