openbsd/src/regress/lib/libssl/interop, branch OPENBSD_6_9_BASEA mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_6_9_BASE2020-12-25T10:50:08+00:00Add to *FLAGS and *ADD rather than overwriting them2020-12-25T10:50:08+00:00tb2020-12-25T10:50:08+00:00urn:sha1:2cc3e262414425825b3c19ff586f2c2cc20bccd2
This makes CFLAGS pick up -O2, which shaves a few seconds runtime
off these very slow tests.
Remove echo headlines.2020-12-17T00:51:12+00:00bluhm2020-12-17T00:51:12+00:00urn:sha1:c7cbfcf2a0ad5dc204129e5fbf99dd57cc33e72abotan2 uses C++11, so use ports-gcc on gcc-archs2020-10-30T03:12:40+00:00tb2020-10-30T03:12:40+00:00urn:sha1:641a04692ce38bf174dd730b7180e766bdaff878
This makes this interop test pass on sparc64.
Do not fail with obscure error messages on 'make'2020-10-29T06:05:12+00:00tb2020-10-29T06:05:12+00:00urn:sha1:1822c50c29255a6f1fb43434b5b68915ea021a20
Fix some tests that fail with obscure error messages on 'make' if the
required package (either version of OpenSSL or Botan 2) isn't installed.
This can be avoided by doing 'make regress' instead. I'll try to adjust
my finger memory for the many tests outside the LibreSSL tree that have
the same "problem". The fix here is unintrusive and I've been wasting
enough time with this to want to change it.
ok bluhm
1) Move the interop tests to the end so we see tlsfuzzer first2020-09-21T15:13:24+00:00beck2020-09-21T15:13:24+00:00urn:sha1:9d558960cf920187dcf488f05a3decde546bbddc
2) Reorder the interop tests so the really slow "cert" test is at the end
3) Change the cert tests to use REGRESS_SLOW_TARGETS when testing combination
of client and server that does not involve libressl. This way we can
skip testing openssl to openssl11 when running these manually by
setting REGRESS_SKIP_SLOW to "yet" in mk.conf
ok jsing@
Test botan TLS client with libressl, openssl, openssl11 server.2020-09-15T01:45:16+00:00bluhm2020-09-15T01:45:16+00:00urn:sha1:99c305e9a1574d8ffff5ba4752c88b964c0fafbdConnect a client to a server. Both can be current libressl, or2020-09-14T00:51:04+00:00bluhm2020-09-14T00:51:04+00:00urn:sha1:407ed00262824449401bb81ab8981bc63ea02280
openssl 1.0.2, or openssl 1.1. Pin client or server to a fixed TLS
version number. Incompatible versions must fail. Check that client
and server have used correct version by grepping in their session
print out.
If CPU does not support AES-NI, LibreSSL TLS 1.3 client prefers2020-09-12T15:48:30+00:00bluhm2020-09-12T15:48:30+00:00urn:sha1:e0ab7f11dbb9b75ca3e654c6a2b285049e1c7afc
chacha-poly over aes-gcm. Expect both fallbacks for non 1.3 ciphers.
Enable cert and cipher interop tests. cert just works. cipher has2020-09-11T22:48:00+00:00bluhm2020-09-11T22:48:00+00:00urn:sha1:66b3b0fa0e26b882333bdd906d8811b1f4094144
been fixed to work with libressl TLS 1.3. Both libressl and openssl11
replace obsolete TLS 1.2 ciphers with AEAD-AES256-GCM-SHA384 or
TLS_AES_256_GCM_SHA384 in TLS 1.3 respectively. The test expects
that now. Currently GOST does not work with libressl and TLS 1.3
and is disabled.
Revise regress for TLSv1.3 server being enabled.2020-05-11T18:20:24+00:00jsing2020-05-11T18:20:24+00:00urn:sha1:9cb614ecfae85e33f73e37c50b4b124384f3403e