wireguard-openbsd/regress/lib/libssl/ssl, branch jd/simplify-queueing WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/lib/libssl/ssl?h=jd%2Fsimplify-queueing 2020-04-09T17:55:45Z Revise test to handle the fact that TLSv1.3 cipher suites are now being 2020-04-09T17:55:45Z jsing jsing@openbsd.org 2020-04-09T17:55:45Z urn:sha1:be86402ee4913eee82cca41f44b3baac06d213bb included in the output from `openssl ciphers`. Test both SSLv3 (aka pre-TLSv1.2) and TLSv1.2 cipher suites with TLS. 2020-04-09T17:27:11Z jsing jsing@openbsd.org 2020-04-09T17:27:11Z urn:sha1:6a37ed6a61b727081f280b6967ef90bb634ac940 exitting -> exiting 2019-04-07T16:41:16Z tb tb@openbsd.org 2019-04-07T16:41:16Z urn:sha1:e4c7564ca5a8e1ce2de3e889835221330a7973d5 From Michael Scovetta, PR #108 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@ Remove NPN test coverage. 2017-08-12T21:05:06Z jsing jsing@openbsd.org 2017-08-12T21:05:06Z urn:sha1:06acd9fc02de8a224dc60d354db98ba1ff0cd245 Treat "ERROR in STARTUP" as an actual error, rather than failing without 2017-03-04T12:53:14Z jsing jsing@openbsd.org 2017-03-04T12:53:14Z urn:sha1:b963adf1cb5fa23c45648d2d7c1e9960b4ad6271 exiting non-zero (which has been masking a DTLS related issue). Also make the message consistent with other errors. Spotted by inogochi@ Remove commented out code and fix indentation of surrounding statements. 2017-03-04T12:47:45Z jsing jsing@openbsd.org 2017-03-04T12:47:45Z urn:sha1:93b15c7e1525a32676401130463f1a061ca67b44 Remove handling for SSLv2. 2017-03-04T12:43:38Z jsing jsing@openbsd.org 2017-03-04T12:43:38Z urn:sha1:154f950aaa01fbdde72273fc79dedc1a649bddbe Use prime256v1 for tests unless otherwise specified. 2017-01-24T06:45:39Z jsing jsing@openbsd.org 2017-01-24T06:45:39Z urn:sha1:725d18cc547c5fb12d8f1d0a57b9eea652534173 check if openssl(1) actually works before proceeding 2015-09-27T18:20:18Z bcook bcook@openbsd.org 2015-09-27T18:20:18Z urn:sha1:c3b429492a453982069280bba51aee081162e4e8 It was possible for this test to pass even if the openssl command itself was missing.