A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE 2018-11-28T15:51:32+00:00 2018-11-28T15:51:32+00:00 jsing 2018-11-28T15:51:32+00:00 urn:sha1:9146b9f89715c0fa5039dde262a76e29bf0be7e1 The current crypto_lock_init() function is not called early enough, meaning that locks are already in use before it gets called. Worse, locks could be in use when they are then initialised. Furthermore, since functions like CRYPTO_lock() are public API, these could be called directly bypassing initialisation. Avoid these issues by using static initialisers. ok bcook@ 2018-11-11T06:41:28+00:00 bcook 2018-11-11T06:41:28+00:00 urn:sha1:3c41ae7ec959c3c608931951c8655a0e1df18696 This implements automatic thread support initialization in libcrypto. This does not remove any functions from the ABI, but does turn them into no-ops. Stub implementations of pthread_mutex_(init|lock|unlock) are provided for ramdisks. This does not implement the new OpenSSL 1.1 thread API internally, keeping the original CRYTPO_lock / CRYPTO_add_lock functions for library locking. For -portable, crypto_lock.c can be reimplemented with OS-specific primitives as needed. ok beck@, tb@, looks sane guenther@