wireguard-openbsd/lib/libcrypto/arch/sh, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/lib/libcrypto/arch/sh?h=jd%2Fqueueboosts 2016-11-04T13:56:04Z 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@ Disable ENGINE_load_dynamic (dynamic engine support). 2015-06-19T06:05:11Z bcook bcook@openbsd.org 2015-06-19T06:05:11Z urn:sha1:9b08b2044f70fb2b1351755a86e57b1ab331448c We do not build, test or ship any dynamic engines, so we can remove the dynamic engine loader as well. This leaves a stub initialization function in its place. ok beck@, reyk@, miod@ i'm a dumbdumb. fix build. 2014-07-11T14:32:59Z tedu tedu@openbsd.org 2014-07-11T14:32:59Z urn:sha1:2d03d1cb16f932679be3ce45b285fa08b24b740d move all the feature settings to a common header. 2014-07-11T14:01:38Z tedu tedu@openbsd.org 2014-07-11T14:01:38Z urn:sha1:5e5c016ed07331adde9d77d6745a6e2a3f77889b probably ok beck jsing miod Make sure we leave OPENSSL_NO_PSK in the conf files so things 2014-07-11T11:41:24Z beck beck@openbsd.org 2014-07-11T11:41:24Z urn:sha1:1e398d8bd7bb98dd7b4c0cd8f9958683b5829812 can know... ok jsing@ first round of static config. ok miod 2014-04-18T18:08:36Z tedu tedu@openbsd.org 2014-04-18T18:08:36Z urn:sha1:8769a7ad17adb9846a6c64508da3078ef82f7560 The more you remove Chtulhu^WVMS tentacles, the more there are 2014-04-15T21:17:14Z miod miod@openbsd.org 2014-04-15T21:17:14Z urn:sha1:512e53b575bf299b0a7f54f505b9fe4662c17e36 Move build machinery for libcrypto from libssl/crypto to libcrypto, as well 2014-04-11T22:51:51Z miod miod@openbsd.org 2014-04-11T22:51:51Z urn:sha1:252ab50e97329c98e35321ea2ec8c92fe431ade1 as configuration files; split manpages and .pc files between libcrypto and libssl. No functional change, only there to make engineering easier, and libcrypto sources are still found in libssl/src/crypto at the moment. ok reyk@, also discussed with deraadt@ beck@ and the usual crypto suspects.