| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
| |
prompted by the bug krw@ fixed yesterday in uuid_from_string()
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Instead of using s_client and s_server and complicated shell scripts,
we can reuse the framework from the ssl_get_shared_cipher() regress
test and inspect the verify return value directly.
Discussed with beck jan jsing
|
| |
|
|
|
|
|
|
| |
generate certdirs by jsing, and make chicken sacrifies by tb.
ok tb@ jsing@
|
| |
|
| |
|
|
|
|
| |
Part of Github PR #105
|
| |
|
|
|
|
| |
ok bluhm@
|
| |
|
|
|
|
| |
suggested by millert@
|
|
|
|
|
| |
This code no longer compiles and the equivalent test coverage has been
added to regress/lib/libssl/ciphers (and is actually run).
|
| |
|
|
|
|
|
|
| |
The get_cipher_by_char() and put_cipher_by_char() pointers are no longer
accessible on the SSL_METHOD (and soon will not even exist). Rewrite the
test to use SSL_CIPHER_find() instead.
|
|
|
|
| |
end statements with ';' because ',' isn't enough
|
|
|
|
| |
This should be moved to a dedicated regress test.
|
|
|
|
| |
We'll either fix these or remove them in the near future.
|
| |
|
|
|
|
|
|
| |
This is a little bit clunky due to the number of things that vary (largely
thanks to middlebox compatibility mode, along with the versions and key
share extensions), however it works and can be improved at a later date.
|
| |
|
| |
|
|
|
|
|
| |
This allows differences between the received data and the test data to be
more readily identified.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
In particular, test handling of 0xfffe and 0xffff - the latter results in
wrapping to zero for the next epoch. One of these tests triggers a known
bug in libssl, which will be fixed following this commit.
|
|
|
|
|
| |
These tests exercise the various queues and delayed processing that exists
in the DTLS code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Two tests currently fail (and are disabled) due to a flaw in the DTLSv1.0
specification - this flaw was addressed in DTLSv1.2, however our DTLS
server code still needs to support the fix.
Quoting RFC 6347 section 4.2.4:
"This requirement applies to DTLS 1.0 as well, and though not explicit in
[DTLS1], it was always required for the state machine to function
correctly."
In otherwords, both the original DTLS implementation and the DTLSv1.0
specification have a broken state machine, resulting in possible dead lock.
|
|
|
|
|
| |
Add a test that delays the client CCS, resulting in it arriving after the
client Finished message.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
did not terminate anymore on some machines. The test counts 100
send errors before it finishes. NetBSD has added sched_yield() in
the receiver loop to trigger the errors on the sender side. Although
not perfect, it works for me. Get current t_sendrecv.c from NetBSD.
|
| |
|
| |
|
|
|
|
| |
discussed and input from jsing@
|
|
|
|
|
|
|
| |
- Split out the intermediate path (../certs/) to Makefile
- Change 'shutdown' to 'shutdown_all'
ok tb@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test depends on the ruby/ruby-openssl-tests port that bundles the
sources and tests of the Ruby OpenSSL gem below /usr/local. The Makefile
compiles the openssl.so shared object below obj/ that provides Ruby
bindings for the OpenSSL API. Once this is built, the regression tests are
run.
There are currently 4 failing tests, all related to the new verifier.
At least one libssl bug is hidden behind a pend. All this will hopefully be
fixed during this release cycle.
This adds a decent amount of test coverage without being overly expensive.
This way, regressions should be spotted during development so jeremy will
no longer have to chase and work around them.
Joint work with jeremy, positive feedback from bcook and jsing.
|
| |
|
| |
|
|
|
|
| |
of points on secp256r1.
|
|
|
|
| |
string representations of points on the binary curve sect571k1.
|
|
|
|
|
|
|
|
|
|
|
| |
wildcards. While we may choose not to support them the standards
appear to permit them optionally so we can't declare a certificate
containing them invalid. Noticed by jeremy@, and Steffan Ulrich
and others. Modify the regression tests to test these cases and
not check the SAN DNSnames as "hostnames" anymore (which don't support
wildcards).
ok jsing@, tb@
|
|
|
|
|
| |
"drop extended_master_secret in renegotiation" since we don't
support this extension.
|
|
|
|
|
| |
via point2oct and oct2point and that checks the corner case in hybrid
encoding that was fixed in ec2_oct.c r1.13.
|