Searched refs:locking (Results 1 – 18 of 18) sorted by relevance
/openssl-master/crypto/evp/ |
A D | keymgmt_lib.c | 220 int evp_keymgmt_util_clear_operation_cache(EVP_PKEY *pk, int locking) in evp_keymgmt_util_clear_operation_cache() argument 223 if (locking && pk->lock != NULL && !CRYPTO_THREAD_write_lock(pk->lock)) in evp_keymgmt_util_clear_operation_cache() 227 if (locking && pk->lock != NULL) in evp_keymgmt_util_clear_operation_cache()
|
/openssl-master/doc/internal/man3/ |
A D | evp_keymgmt_util_export_to_provider.pod | 26 int evp_keymgmt_util_clear_operation_cache(EVP_PKEY *pk, int locking); 53 clear the cache of operation key references. If I<locking> is set to 1 then
|
/openssl-master/doc/man3/ |
A D | X509_STORE_new.pod | 7 - X509_STORE allocation, freeing and locking functions
|
A D | BN_CTX_new.pod | 45 locking is performed, and the internal pool allocator will not properly handle
|
A D | EVP_RAND.pod | 160 EVP_RAND_enable_locking() enables locking for the RAND I<ctx> and all of 163 I<ctx> from multiple threads. Typically locking should be enabled before a 338 An B<EVP_RAND_CTX> needs to have locking enabled if it acts as the parent of
|
A D | BN_BLINDING_new.pod | 66 provide proper locking if needed for multi-threaded use.
|
A D | CRYPTO_THREAD_run_once.pod | 50 which can then be used with the locking functions below.
|
A D | BIO_s_bio.pod | 36 since no locking is done on the internal data structures.
|
/openssl-master/doc/man7/ |
A D | openssl-threads.pod | 75 will do any necessary locking. 76 Some API's, such as L<NCONF_load(3)> and related do no locking at all;
|
A D | EVP_RAND.pod | 104 by its child DRBG instances. The necessary locking is done internally. 109 locking via the EVP_RAND interface. 117 All other DRBG instances created by an application don't support locking, 135 RAND_add() ==> <primary> <-| shared DRBG (with locking) |
|
A D | provider-rand.pod | 139 When DRBGs are used by multiple threads, there must be locking employed to 140 ensure their proper operation. Because locking introduces an overhead, it 143 OSSL_FUNC_rand_enable_locking() allows locking to be turned on for a DRBG and all of
|
/openssl-master/include/openssl/ |
A D | crypto.h.in | 255 * The old locking functions have been removed completely without compatibility 258 * Replacing the locking functions with no-ops would cause race condition 261 * On the other hand, the locking callbacks are no longer used. Consequently, 271 * These defines where used in combination with the old locking callbacks,
|
/openssl-master/crypto/property/ |
A D | README.md | 63 per algorithm locking being used for longer intervals.
|
/openssl-master/crypto/err/ |
A D | openssl.txt | 700 EVP_R_LOCKING_NOT_SUPPORTED:213:locking not supported 732 EVP_R_UNABLE_TO_ENABLE_LOCKING:212:unable to enable locking 1049 PROV_R_PARENT_LOCKING_NOT_ENABLED:182:parent locking not enabled 1108 RAND_R_PARENT_LOCKING_NOT_ENABLED:130:parent locking not enabled
|
/openssl-master/include/crypto/ |
A D | evp.h | 784 int evp_keymgmt_util_clear_operation_cache(EVP_PKEY *pk, int locking);
|
/openssl-master/doc/man1/ |
A D | openssl-ts.pod.in | 616 server module, it does proper locking.
|
A D | openssl-ca.pod.in | 783 This command command is effectively a single user command: no locking
|
/openssl-master/ |
A D | CHANGES.md | 5565 ARMv5 through ARMv8, as opposite to "locking" it to single one. 9226 * Fix X509_STORE locking: Every 'objs' access requires a lock (to 9486 obligation to set up the dynamic locking callbacks.) 9533 double-checked locking was incomplete for RSA blinding, 9535 doubly unsafe triple-checked locking. 11549 avoids excessive locking; and if an RSA object is not shared 11688 make such changes in the libcrypto locking code that changes will 13389 * Add functionality to `apps/openssl.c` for detecting locking 13391 to do is register a locking callback using an array for 13807 avoids excessive locking; and if an RSA object is not shared [all …]
|
Completed in 620 milliseconds