summaryrefslogtreecommitdiff
path: root/src/regress/lib/libssl (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Update record regress to match functionality changes.jsing2019-01-201-6/+37
|
* hook handshake testtb2019-01-201-1/+2
|
* Add a simple test that verifies that every valid handshaketb2019-01-202-0/+76
| | | | sets action->handshake_complete.
* Hook record regress.jsing2019-01-191-1/+3
|
* Add regress for TLSv1.3 record handling.jsing2019-01-192-0/+533
|
* initialize offset value so this passesbeck2019-01-181-0/+1
| | | | ok jsing@
* Add client side of supported versions and keyshare extensions with basic regressbeck2019-01-181-1/+192
| | | | ok jsing@
* Removed unused struct members.jsing2019-01-181-2/+0
|
* Update regress following TLS extension renaming.jsing2019-01-182-379/+378
|
* Add regress for extensible buffer code.jsing2019-01-173-1/+169
|
* Just err if we can't create secretsbeck2018-11-131-2/+2
|
* Fix a race in libssl interop regress. The success messages frombluhm2018-11-113-6/+9
| | | | | the server child could be delayed. In this case wait a second and check again.
* Add automatic threading initialization for libcrypto.bcook2018-11-111-56/+0
| | | | | | | | | | | | | | 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@
* Reorganize libssl interop tests. Move netcat tests into separatebluhm2018-11-119-148/+197
| | | | | directory. Keep all log files for easier debugging. Name regress target names consistently.
* Spelingbeck2018-11-101-2/+2
|
* Regress client and server can do session reuse now. Test this withbluhm2018-11-106-129/+220
| | | | | all combinations of LibreSSL, OpenSSL 1.0.2, and OpenSSL 1.1. It is currently disabled for TLS 1.3 as this needs more setup.
* Make sure the interop test happen last (since they take a long time)beck2018-11-102-8/+9
|
* fix a leak reported by Ben L (bobsayshilol () live ! co ! uk)tb2018-11-101-1/+3
|
* More regress all the way to exporter_masterbeck2018-11-101-4/+44
|
* Fix last of the empty hash nonsensebeck2018-11-101-6/+3
| | | | ok jsing@
* Update key schedule regress to match API changes.jsing2018-11-091-21/+12
|
* remove the not yet implemented "handshake" subdirectorytb2018-11-091-2/+1
|
* Add subdirectires with SUBDIR += instead of a single assignment withtb2018-11-091-13/+13
| | | | line continuations.
* The cert subdir is testing all combinations of certificate validation.bluhm2018-11-0911-48/+244
| | | | | | Having the three libraries, client and server certificates, missing or invalid CA or certificates, and enforcing peer certificate results in 1944 new test cases.
* Add in key_schedule regress tests to regress buildbeck2018-11-071-1/+2
|
* Add a self test for each SSL library by connecting client withbluhm2018-11-075-23/+88
| | | | | | server. Check that the highest available TLS version is selected. LibreSSL TLS 1.3 check is disabled until the feature becomes available.
* Add initial TLS 1.3 key schedule support with basic regress testsbeck2018-11-072-0/+249
| | | | ok jsing@ tb@
* Add interop test with OpenSSL 1.1. TLS 1.3 should be used automaticallybluhm2018-11-075-10/+55
| | | | | when it becomes available in LibreSSL. thanks to sthen@ for the new OpenSSL port
* Print SSLeay, OpenSSL, and LibreSSL version strings. Make clientbluhm2018-11-077-12/+71
| | | | | and server compile with OpenSSL 1.1. Check runtime version string of SSL library.
* +interopbluhm2018-11-071-1/+2
|
* Test TLS interoperability between LibreSSL and OpenSSL.bluhm2018-11-0710-0/+549
| | | | | | | | | | | | Implement simple SSL client and server in C. Create four binaries by linking them with LibreSSL or OpenSSL. This way API compatibility is tested. Connect and accept with netcat to test protocol compatibility with libtls. Currently OpenSSL 1.0.2p from ports is used. Plan is to move to OpenSSL 1.1 and and test TLS 1.3. idea from beck@; help from jsing@
* Add TLSv1.3 to version regress tests.jsing2018-11-061-4/+80
|
* Unbreak regress following Supported Elliptic Curve extension rename.jsing2018-11-061-49/+49
|
* Add regress coverage for CBB_add_u32().jsing2018-08-161-3/+4
|
* Update regress for DES cipher suite removal.jsing2018-06-022-49/+41
|
* Zero the client random so that it is easier to spot unintended differences.jsing2018-06-021-0/+1
|
* Provide SSL_CTX_get_min_proto_version and SSL_CTX_get_max_proto_versionjca2018-03-151-13/+13
| | | | | | | | | We already provided the setters, so also provide the getters like OpenSSL does. Addition prompted by the use of those functions in recent openvpn releases. manpage diff from schwarze@ (thanks!) with input from jsing@, ok tb@ jsing@
* Update regress to use tlsext_serverhello_parse().jsing2018-02-081-5/+3
|
* Update regress to match removal of ssl_parse_clienthello_tlsext().jsing2018-01-271-5/+8
|
* Initialise new_cipher in the serverhello TLS extensions test, to avoid ajsing2017-12-281-3/+14
| | | | | | | | | | NULL pointer dereference in ssl_using_ecc_cipher(). Some compilers avoid triggering this, likely due to the EC formats list also being NULL. While here, setup the EC formats list so that we actually include the EC points format extension in the server hello extensions. Found the hard way by bcook@
* Add regress test coverage for building clienthello and serverhellojsing2017-11-281-4/+201
| | | | | extensions, both with extensions being present and not present. The not present case currently fails.
* Add regress for CBB_discard_child().jsing2017-11-281-2/+56
| | | | Converted from BoringSSL.
* Update regress now that ssl_cipher_list_to_bytes() takes a CBB.jsing2017-10-111-3/+9
| | | | Based on a diff from doug@
* Revise regress now that ssl_bytes_to_cipher_list() takes a CBS.jsing2017-10-101-20/+10
|
* When parsing extensions by calling the parse functions directly, ensurejsing2017-08-291-2/+82
| | | | | that we have consumed all of the extension data. This catches the ALPN extension handling issue that was just fixed.
* Use current chacha20-poly1305 cipher suite values.jsing2017-08-281-7/+7
|
* Update due to removal of original chacha20-poly1305 cipher suites.jsing2017-08-281-42/+39
|
* Rewrite SRTP extension using CBB/CBS and the new extension framework.doug2017-08-271-1/+402
| | | | input + ok beck@, jsing@
* check return value from CBB_initbeck2017-08-271-2/+3
|
* Rewrite ALPN extension using CBB/CBS and the new extension framework.doug2017-08-261-1/+381
| | | | | ok bcook@ beck@ input + ok jsing@