summaryrefslogtreecommitdiff
path: root/src/regress/lib (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* rust-openssl: switch from deprecated config to config.tomltb2024-06-232-2/+2
|
* Add regress coverage for X509V3_get_d2i()tb2024-06-171-1/+265
|
* zap a stray spacetb2024-06-161-2/+2
|
* openssl-ruby: prepare test for default ruby switchtb2024-06-151-1/+5
|
* make test struct consttb2024-06-051-3/+3
|
* Adjust hmac test for removal of static buffer from HMAC()tb2024-05-301-2/+2
|
* asn1object: zap trailing whitespacetb2024-05-291-3/+3
|
* Make it possible for the large OID test to failtb2024-05-291-3/+3
| | | | | | failed was set to 0 at the top of the function, so failure and success were indistinguishable. Move failed = 0 to the end so it can actually fail.
* Add regress coverage for some corner cases of i2d_ASN1_OBJECT()tb2024-05-291-1/+40
|
* Add regress coverage for i2d_ASN1_OBJECT() fixestb2024-05-291-3/+27
|
* Test that invalid operations push the X509V3_R_UNSUPPORTED_OPTION errortb2024-05-281-1/+53
|
* Add regress coverage for X509V3_add1_i2d()tb2024-05-282-2/+605
|
* Eliminate last timegm() correctly this timetb2024-05-251-5/+25
| | | | | Also add a test case with a generalized time representing the moment one second past the 32-bit epoch wrap.
* Revert previoustb2024-05-251-10/+4
| | | | It wasn't quite right, but I also think the test is bogus.
* asn1time: another use of gmtime was hiding heretb2024-05-251-4/+10
|
* Exercise EVP_chacha20_poly1305() with in-place decryptiontb2024-05-221-2/+143
| | | | | This needs quite a bit of cleanup but let's have some tests rather than none.
* Add more regress coverage for lhash.jsing2024-05-081-3/+263
|
* symbols test: drop headers that don't define any symbolstb2024-05-081-4/+1
|
* Enable lhash regress.jsing2024-05-061-1/+2
|
* Provide initial regress for lhash.jsing2024-05-062-0/+71
| | | | | | For now, this is very limited and only tests calling lh_doall_arg() multiple times on an empty linked hash. This process currently triggers a SIGSEGV, which will be soon fixed.
* Add regress coverage for crypto_ct_*_u8()jsing2024-04-253-1/+111
|
* Instead of unhooking libssl/client regress tests, flag them as expectedanton2024-04-222-4/+6
| | | | | | to fail. ok tb@
* SSL_version_str is no moretb2024-04-171-5/+1
|
* Add regress coverage for BN_lebin2bn().jsing2024-04-171-3/+17
|
* Remove workarounds for unprototyped symbolstb2024-04-151-71/+1
|
* Enable negative zero checks for BN_clear_bit() and BN_mask_bits().jsing2024-04-151-5/+1
|
* t22 and t23 can fail if the first chunk ends up being allocated atotto2024-04-141-2/+12
| | | | | the very end of the page. Circumvent that. Reported by and fix ok anton@
* symbols test: Remove a few things that are long gonetb2024-04-101-19/+5
|
* whirlpool_test: avoid calling arc4random_uniform(0)tb2024-04-091-2/+4
| | | | | This causes a SIGFPE on solaris Fixes https://github.com/libressl/portable/issues/1042
* whirlpool_test: zap lots of trailing whitespacetb2024-04-091-58/+58
|
* bn_convert: plug leak spotted by ASANtb2024-04-091-2/+4
|
* Add initial regress for BN_set_bit(), BN_clear_bit() and BN_mask_bits().jsing2024-04-092-1/+229
|
* Add regress coverage for BN_bn2mpi()/BN_mpi2bn().jsing2024-04-091-6/+123
|
* Make ASN1_TIME_set_string_X509 and ASN1_TIME_set_string match the man pagebeck2024-04-082-13/+46
| | | | | | | | | | | This makes it where people can't put dumb values in certs without trying harder, and changes the regress to test this. GENERALIZED times outside of the RFC5280 spec are required for OCSP but these should be constructed with the GENERALIZED time string setters. ok tb@
* Initialize quic_method in tlsexttesttb2024-03-301-3/+3
| | | | | | | This is only there to pretend a quic method was set on the SSL, but apparently some compilers warn about an uninitialized variable. from Christian Andersen
* Replace silly test1_exit() with exit()tb2024-03-301-21/+15
| | | | | | Appeases some compiler. from Christian Andersen
* Remove call to lh_FUNCTION_free()tb2024-03-301-3/+1
| | | | | | This is a wrapper around lh_free() which is already tested. From Christian Andersen
* Do multiple padding add/check iterations.jsing2024-03-301-24/+34
| | | | | This increases the chance of triggering bugs due to input and/or randomised padding.
* Add initial regress for RSA padding.jsing2024-03-302-2/+328
|
* Tidy indentation.jsing2024-03-302-8/+8
| | | | Requested by tb@
* Remove -app2_1 flags being passed to dsa and rsa regress.jsing2024-03-302-14/+2
| | | | Nothing does flag handling in these tests.
* Add table-driven Whirlpool testsjoshua2024-03-293-1/+251
| | | | ok tb
* Add regress coverage for EdDSA in CMStb2024-03-291-6/+42
|
* Remove CMS special now that we do not depend on pem.h being included first.jsing2024-03-291-2/+1
|
* Nuke more gostbeck2024-03-282-0/+0
|
* Nuke more leftover GOST tendrils.beck2024-03-283-1497/+1
| | | | ok tb@
* Fix coverity complaints.beck2024-03-281-4/+6
|
* fix leaks in the horrible ssl whackery necessary for this test.beck2024-03-271-4/+5
| | | | ok tb@
* Fix up server processing of key shares.beck2024-03-271-5/+96
| | | | | | | | | | | | | | | | | | | Ensure that the client can not provide a duplicate key share for any group, or send more key shares than groups they support. Ensure that the key shares must be provided in the same order as the client preference order specified in supported_groups. Ensure we only will choose to use a key share that is for the most preferred group by the client that we also support, to avoid the client being downgraded by sending a less preferred key share. If we do not end up with a key share for the most preferred mutually supported group, will then do a hello retry request selecting that group. Add regress for this to regress/tlsext/tlsexttest.c ok jsing@
* Fix expected client hello value to allow for supported_groups change.beck2024-03-261-4/+4
| | | | ok jsing@