summaryrefslogtreecommitdiff
path: root/src/regress (follow)
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Some style(9).jsing2017-08-281-3/+6
|
* Remove chacha20-poly1305-old regress and test vectors.jsing2017-08-282-627/+0
|
* 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@
* test locale priorities and overridesschwarze2017-08-161-1/+36
|
* test isalpha_l(3), tolower_l(3), wctype_l(3), iswctype_l(3),schwarze2017-08-161-4/+149
| | | | | wctrans_l(3), towctrans_l(3), wcscasecmp_l(3), wcsncasecmp_l(3), and strerror_l(3)
* test nl_langinfo_l(3), iswalpha_l(3), towupper_l(3)schwarze2017-08-162-3/+44
|
* refactor in preparation for testing more functions; no functional changeschwarze2017-08-152-114/+117
|
* Rewrite the TLS status request extension to use the new TLS extension framework.beck2017-08-121-1/+128
| | | | ok jsing@
* Add regress coverage for the TLS signature algorithms extension.jsing2017-08-121-1/+163
|
* Rewrite session ticket TLS extension handling using CBB/CBS and the newdoug2017-08-121-1/+302
| | | | | | extension framework. ok jsing@ beck@
* Remove NPN test coverage.jsing2017-08-122-129/+1
|
* errant whitespacebeck2017-08-121-3/+3
|
* fix resource leaks, ok @guentherbcook2017-08-121-3/+7
|
* Update the TLSv1.2 Client Hello messages, due to the removal of DSAjsing2017-08-121-20/+18
| | | | sigalgs.
* Be consistent with goto labels, failure flag and use of FAIL macro.jsing2017-08-111-128/+105
|
* doug@ added code in here as well.jsing2017-08-111-1/+2
|
* Sort by extension/function name.jsing2017-08-111-577/+576
|
* Rewrite EllipticCurves TLS extension handling using CBB/CBS and the newdoug2017-08-111-1/+337
| | | | | | extension framework. input + ok jsing@
* Rewrite the ECPointFormats TLS extension handling using CBB/CBS and thedoug2017-08-111-1/+470
| | | | | | new extension framework. input + ok jsing@
* first draft of tests for newlocale(3), duplocale(3), uselocale(3)schwarze2017-08-102-0/+268
|
* Sort subdir, run getaddrinfo test, remove vax case.bluhm2017-07-271-13/+21
|
* Sort expected getaddrinfo output in inet4 inet6 order, then thebluhm2017-07-272-46/+37
| | | | test passes.
* Fix all clang warnings in libc regress and cleanup some make files.bluhm2017-07-2718-75/+67
|
* Mark the invalid memory location as volatile, otherwise clang wouldbluhm2017-07-271-2/+2
| | | | | optimize the access to it with an illegal instruction. But the tests needs a SIGSEGV, it would fail with SIGILL.
* Extend the SNI tests to ensure that we have a hostname in the sessionjsing2017-07-241-2/+31
| | | | | | after a successful tlsext_sni_serverhello_parse() and that tlsext_sni_clienthello_parse() fails if we have an existing session and the SNI is mismatched.
* Add regress coverage for the TLS Renegotiation Indication extension.jsing2017-07-241-1/+266
|
* Provide a new regress test for TLS extension handlers, currently coveringjsing2017-07-163-1/+256
| | | | the newly converted SNI code.
* Add a test that covers the recently fixed "0x" prefix handling issue.jsing2017-07-151-1/+2
|
* Run malloc0test with all possible malloc options.bluhm2017-07-081-1/+7
|
* Also test arrays of double and long long.millert2017-05-271-142/+421
|
* Synchronise chacha test cases with the referenced draft - this adds ajsing2017-05-261-23/+23
| | | | | | | | missing test case, reassigns two of the labels and removes a test case that was from an earlier draft. Inconsistency noted by Steven Roberts <fenderq at gmail dot com>, some time ago...
* Add timing and test name options.millert2017-05-221-12/+83
|
* Instead of embedding pre-generated tables from McIlroy's "A Killermillert2017-05-223-1538/+315
| | | | | Adversary for Quicksort", just include the code to generate them. Also allow the number of elements to be specified on the command line.
* correct a return value testjsg2017-05-211-1/+1
| | | | ok millert@
* Add input targeted at the Bentley and McIrlroy quicksort generatedmillert2017-05-191-6/+1389
| | | | | by McIlroy's "A Killer Adversary for Quicksort". This results in quadratic behavior and the test aborts before completion.
* use mergesort instead of heapsort when comparing resultsmillert2017-05-181-9/+17
|
* Avoid running the "killer" tests multiple times with the samemillert2017-05-171-10/+19
| | | | parameters.
* Add "median of three" killer, as seen in "Introspective Sorting andmillert2017-05-171-18/+44
| | | | Selection Algorithms" by David R Musser.
* Approximate nlgn instead of using libm. The same approximation maymillert2017-05-172-10/+8
| | | | be used in qsort.c in a later commit.
* Add "killer" input from "algorithmic complexity attacks and libcmillert2017-05-171-0/+12
| | | | | | | qsort()". This causes quadratic behavior with the 4.4BSD qsort's "switch to insertion sort" optimization when the input appears to be mostly sorted. That optimization was removed in qsort.c r1.12 but it is worth having in the regress test too.
* There's no need to track the number of errors (and the counter mightmillert2017-05-171-21/+30
| | | | wrap), make it a flag instead. Pointed out by schwarze@
* Add qsort(3) regress based on Bentley & McIlroy's "Engineering a Sort Function"millert2017-05-173-2/+278
|
* Revise cipher suites in regress to match DSS cipher suite removal.jsing2017-05-071-96/+82
|
* Add a (currently failing) call to tls_handshake() on a client context thatjsing2017-05-071-1/+8
| | | | | has not yet been connected. We expect this to fail, but it should fail gracefully.
* Also test calling tls_handshake() on a server connection context that hasjsing2017-05-071-1/+7
| | | | already completed a TLS handshake.