Searched refs:lock (Results 76 – 83 of 83) sorted by relevance
1234
418 BN_MONT_CTX *BN_MONT_CTX_set_locked(BN_MONT_CTX **pmont, CRYPTO_RWLOCK *lock,
683 CRYPTO_RWLOCK *lock; member
123 will lock the <primary> DRBG automatically for obtaining random input.
147 OSSL_FUNC_rand_lock() is used to lock a DRBG. Once locked, exclusive access
1094 CRYPTO_RWLOCK *lock; member1194 CRYPTO_RWLOCK *lock; member
58 need to be synchronised with a lock, undermining performance on what (for
997 * The OBJ_ calls are now thread safe using a global lock.10032 lock to call BN_BLINDING_invert_ex, and avoids one use of11101 * Fix X509_STORE locking: Every 'objs' access requires a lock (to11102 accommodate for stack sorting, always a write lock!).12019 runtime, thus removing the need for a lock.12036 runtime, thus removing the need for a lock.12645 * Add new lock type (CRYPTO_LOCK_BN).15271 * Use a lock around the call to CRYPTO_get_ex_new_index() in16405 the CRYPTO_LOCK_RAND lock (and may even illegally release the lock17145 not read locks (`CRYPTO_r_[un]lock`).[all …]
663 * The public and private DRBG instance are per thread for lock free
Completed in 88 milliseconds
