Age | Commit message (Collapse) | Author |
|
gcc emits a signed vs unsigned comparison warning which breaks the build
due to -Werror.
|
|
Provide a BIO that can drop specific messages in order to trigger and test
DTLS timeouts and retransmissions. Note that the SSL buffering BIO (bbio)
has to be removed to ensure that handshake messages are sent individually.
This would have detected the recent DTLS breakage with retransmissions for
a flight that includes a CCS.
|
|
In particular, ensure we clear events when the client or server side has
completed and fix timeouts to ensure we use a non-zero timeout if present.
|
|
|
|
Test the operation of a DTLS client and server, with and without cookies,
using the default MTU and a specifically lowered MTU.
Further regress tests will be built on this to exercise other parts of the
DTLS code base (such as retransmission, fragmentation and reassembly).
|
|
|
|
|
|
|
|
|
|
|
|
chain. It only takes a few dozens of ms to read it, but doing this 7290
times adds up to a few minutes run time. This way, the test completes in
a handful of seconds.
Diagnosed by jsing, ok beck
|
|
|
|
|
|
|
|
This includes a test where the server response includes multiple handhshake
messages in the single TLS plaintext record (which would have caught the
bug just fixed in tls13_legacy.c).
|
|
|
|
|
|
|
|
|
|
using the make variable EOPENSSL11.
Suggested by jsing
|
|
|
|
to look at its private headers either.
|
|
The X509_STORE_CTX struct is opaque in OpenSSL 1.1. To avoid reaching
inside it, reuse the trusted certificate store that was just assigned
to it and use X509_STORE_CTX_get0_param(3) to access the verification
parameters.
|
|
|
|
instead of the "decrypt_error" sent by tls13_server_finished_recv().
Both alerts appear to be reasonable in this context, so enable the tests
while working around this.
|
|
|
|
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@
|
|
|
|
failure of x509_constraints_uri_host() in x509_constraints_uri()
|
|
regress to catch it in the future.
found by Guido Vranken's cryptofuzzer
ok tb@
|
|
test compile and pass on sparc64.
|
|
to the beginning of the respective scopes (and out of for loops)
|
|
on sparc64
|
|
|
|
Add a cast to tell gcc 4.2.1 that the return value is deliberately
ignored. This makes the test compile and pass on sparc64.
|
|
Make tests compile and pass on sparc64 with gcc 4.2.1 by properly
declaring "static int foo()" as "static int foo(void)".
|
|
|
|
|
|
This regress parses Symbols.list and pulls all public headers out of
libcrypto's Makefile to generate a simple program that uses all public
symbols. A number of symbols need to be declared extern since they are
unavailable in public headers and a handful must be skipped since they
are apparently architecture dependent.
This would have caught the recent breakage due to the accidental removal
of the NAME_CONSTRAINTS_check() function and points out a number of
places where cleanup may happen in the future.
discussed with beck
|
|
|
|
Noted by bcook@ and inoguchi@ while working on portable.
|
|
|
|
|
|
no longer ignore the expected failures from the legacy name
constraints validation, and will have a regress failure if
we regress.
|
|
have to re-generate these certificates and this should
just keep working even if the certs get old
|
|
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.
|
|
|
|
The new validator finds multiple validated chains to handle the modern
PKI cases which may frequently have multiple paths via different
intermediates to different roots. It is loosely based on golang's x509
validator
This includes integration so that the new validator can be used via
X509_verify_cert() as well as a new api x509_verify() which will
return multiple chains (similar to go).
The new validator is not enabled by default with this commit, this
will be changed in a follow on commit.
The new public API is not yet exposed, and will be finalized and
exposed with a man page and a library minor bump later.
ok tb@ inoguchi@ jsing@
|
|
chacha-poly over aes-gcm. Expect both fallbacks for non 1.3 ciphers.
|
|
|