wireguard-openbsd/lib/libcrypto/cryptlib.c, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/lib/libcrypto/cryptlib.c?h=jd%2Fqueueboosts 2019-01-26T11:30:32Z Recent discussions about abort() potentially leaving key material in 2019-01-26T11:30:32Z deraadt deraadt@openbsd.org 2019-01-26T11:30:32Z urn:sha1:5af5b084743205200c0de76ba78a762e1dc2a008 core files (which can depend upon various file layouts) have resonated with my hate for this function outside a purely debugging context. I also dislike how the report goes to stderr which may get lost or ignored. Increase the noise (with syslog_r) and use _exit(1) to gaurantee termination. ok jsing Store and return the locking callbacks, restoring previous behaviour. 2018-11-24T04:11:47Z jsing jsing@openbsd.org 2018-11-24T04:11:47Z urn:sha1:a457dfe1e50159d324c928ce772e78d03274214d The previous code meant that a caller could set the locking callback, after which CRYPTO_get_locking_callback() would return non-NULL. Some existing code depends on this behaviour, specifically to identify if lock handling has been configured. As such, always returning NULL from CRYPTO_get_locking_callback() can result in unexpected application behaviour. ok bcook@ Add back a few missing compatibility stubs 2018-11-11T16:32:28Z bcook bcook@openbsd.org 2018-11-11T16:32:28Z urn:sha1:e7b19e0e3acead2fddade1bcebf28f4bc40cbd30 ok beck@ Add automatic threading initialization for libcrypto. 2018-11-11T06:41:28Z bcook bcook@openbsd.org 2018-11-11T06:41:28Z urn:sha1:3938ed1ebd7560655156b4463ed629b56b149c35 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@ Stop calling OPENSSL_init() internally, since it is a no-op. Also place 2017-04-29T21:48:43Z jsing jsing@openbsd.org 2017-04-29T21:48:43Z urn:sha1:60e626a589c7097113ddae72add2c15e84acad1d it under #ifndef LIBRESSL_INTERNAL. ok beck@ Send the function codes from the error functions to the bit bucket, 2017-01-29T17:49:22Z beck beck@openbsd.org 2017-01-29T17:49:22Z urn:sha1:5067ae9f807f8af9e6350e51e6a54619386c06ba as was done earlier in libssl. Thanks inoguchi@ for noticing libssl had more reacharounds into this. ok jsing@ inoguchi@ Replace all uses of magic numbers when operating on OPENSSL_ia32_P[] by 2016-11-04T17:30:30Z miod miod@openbsd.org 2016-11-04T17:30:30Z urn:sha1:e60c46c4c9a5c27f2a64a9eeda73a83a36b3f7a8 meaningful constants in a private header file, so that reviewers can actually get a chance to figure out what the code is attempting to do without knowing all cpuid bits. While there, turn it from an array of two 32-bit ints into a properly aligned 64-bit int. Use of OPENSSL_ia32_P is now restricted to the assembler parts. C code will now always use OPENSSL_cpu_caps() and check for the proper bits in the whole 64-bit word it returns. i386 tests and ok jsing@ Remove I386_ONLY define. It was only used to prefer a 2016-11-04T13:56:04Z miod miod@openbsd.org 2016-11-04T13:56:04Z urn:sha1:4647d16fb4cbf0d3331c83027d620ec393564786 faster-on-genuine-80386-but-slower-on-80486-onwards innstruction sequence in the SHA512 code, and had not been enabled in years, if at all. ok tom@ bcook@ Since a major bump of libcrypto is coming, remove OPENSSL_ia32cap and 2015-09-13T16:56:11Z miod miod@openbsd.org 2015-09-13T16:56:11Z urn:sha1:de12ad7f6bf03db8249eb526840df325f439ce56 OPENSSL_ia32cap_loc; nothing in ports uses them besides embedded copies of OpenSSL. This opens the `all hell gets loose' window. Add a new interface, OPENSSL_cpu_caps(), to return the currently running 2015-09-13T10:02:49Z miod miod@openbsd.org 2015-09-13T10:02:49Z urn:sha1:f7e3f7bf3271f1ecb1801257bc19b5f637ec20d5 cpu's specific hardware capabilities users of libcrypto might be interested in, as an integer value. This deprecates the existing OPENSSL_ia32cap() macro and the OPENSSL_ia32cap_loc() function (which returns the pointer so that you can mess with stuff you shouldn't mess with). Interpreting the value returned by OPENSSL_cpu_caps() is, of course, machine-dependent. Minor version bump for libcrypto. ok beck@ jsing@