From 06394a6cc7c784b46bc6d1e65a1ff39637093934 Mon Sep 17 00:00:00 2001 From: Pauli Date: Thu, 24 Jun 2021 23:51:53 +1000 Subject: doc: Document that the OBJ creation functions are now thread safe. With the OBJ_ thread locking in place, these documentation changes are not required. This reverts commit 0218bcdd3feab456135207c140998305df73ab7b. Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/15713) --- doc/man7/provider-base.pod | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'doc/man7') diff --git a/doc/man7/provider-base.pod b/doc/man7/provider-base.pod index d1e26baa11..5af35bf4dc 100644 --- a/doc/man7/provider-base.pod +++ b/doc/man7/provider-base.pod @@ -269,7 +269,6 @@ It will treat as success the case where the OID already exists (even if the short name I or long name I 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) consisting of an underlying signature algorithm (I) @@ -283,7 +282,6 @@ to identify the object. It will treat as success the case where the composite signature algorithm already exists (even if registered against a different underlying signature or digest algorithm). It returns 1 on success or 0 on failure. -This function is not thread safe. CRYPTO_malloc(), CRYPTO_zalloc(), CRYPTO_memdup(), CRYPTO_strdup(), CRYPTO_strndup(), CRYPTO_free(), CRYPTO_clear_free(), @@ -613,6 +611,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 -- cgit v1.2.3