A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE 2023-07-08T08:28:23+00:00 2023-07-08T08:28:23+00:00 beck 2023-07-08T08:28:23+00:00 urn:sha1:842e06ad9bdf75858b4eca096b3f27979b2101fd ok jsing@ 2023-06-04T17:28:35+00:00 tb 2023-06-04T17:28:35+00:00 urn:sha1:383800ed25dd1967077f5e56673b8363dd647b9e This traded local copies of CTASSERT() to the one in crypto_internal.h. This change was backed out due to SHA-512 breakage on STRICT_ALIGNMENT architectures still using Fred Flintstone's gcc without asm sha512. Original commit message: Use crypto_internal.h's CTASSERT() Now that this macro is available in a header, let's use that version rather than copies in several .c files. discussed with jsing 2023-05-19T00:54:28+00:00 deraadt 2023-05-19T00:54:28+00:00 urn:sha1:3dc51b1807e9a69624721300010e6e6ce16d5709 2023-05-17T07:42:38+00:00 tb 2023-05-17T07:42:38+00:00 urn:sha1:11b2caf2d2be047efd96d29f1a2278031692364a Now that this macro is available in a header, let's use that version rather than copies in several .c files. discussed with jsing 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@