openssl
/
openssl
mirror of https://github.com/openssl/openssl
1
0
Fork 0
Code Issues Releases Wiki Activity

doc: add note to indicate that the OBJ_ functions were not thread safe in 3.0 

Also remove OBJ_thread from the list of non-threadsafe functions.

Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/15713)
This commit is contained in:
Pauli 2021-06-11 19:10:49 +10:00 committed by Pauli
parent 06394a6cc7
commit b66b024cf7
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/man7/openssl-threads.pod
View File

@ -73,8 +73,8 @@ For implicit global state or singletons, thread-safety depends on the facility.
The L<CRYPTO_secure_malloc(3)> and related API's have their own lock,
while L<CRYPTO_malloc(3)> assumes the underlying platform allocation
will do any necessary locking.
Some API's, such as L<NCONF_load(3)> and related, or L<OBJ_create(3)>
do no locking at all; this can be considered a bug.
Some API's, such as L<NCONF_load(3)> and related do no locking at all;
this can be considered a bug.
A separate, although related, issue is modifying "factory" objects
when other objects have been created from that.