summaryrefslogtreecommitdiff
path: root/src/regress/lib (follow)
Commit message (Collapse)AuthorAgeFilesLines
* link illumos oclo test to the treetb2025-08-041-2/+2
|
* Provide benchmarks for EC arithmetic.jsing2025-08-032-1/+212
| | | | | This provides benchmarking for EC_POINT_add(), EC_POINT_dbl() and EC_POINT_mul()'s scalar * generator path.
* Provide harness to run illumos's oclo tests from libc regresstb2025-08-023-0/+32
| | | | | | | This depends on the illumos-os-tests port I just imported and can be linked to the build once guenther lands the close-on-fork diff. Adapted from an initial diff by Ricardo Branco
* hash_test: remove variable name from prototype and fix a casttb2025-08-021-3/+3
|
* Retire interop tests with OpenSSL 3.3 and 3.4tb2025-07-259-141/+11
|
* regress/libcrypto/x509/bettertls: switch to eopenssl35tb2025-07-231-4/+4
|
* regress/libcrypto/ec: switch to openssl35tb2025-07-231-4/+4
|
* ec_asn1_test: fix includestb2025-07-231-1/+5
|
* ectest: fix includestb2025-07-231-6/+3
|
* c2sp: unhook openssl 3.3 and 3.4tb2025-07-231-2/+2
|
* libcrypto regress: add interop harness for openssl/3.5tb2025-07-098-10/+75
|
* libcrypto regress: move GOCACHE to obj/tb2025-07-093-12/+28
| | | | | | | | | | | | | While it may be acceptable for Go to fill regular users' homedirs with a compiler cache that is unable to deal with corruption and full disks, this is terrible for people running regress as root since the cache can quickly grow to hundreds of megs and can thus result in all sorts hilarity below /root. Move the GOCACHE under ${.OBJDIR} and use a cleanup target to get rid of it again. This makes these tests a bit slower for regular users as well, but so be it. Let's see how this goes before I switch libtls to the same model. discussed with claudio and jsing
* Add minimal regress coverage for AES-XTSjsing2025-07-051-2/+183
|
* openssl-ruby-tests: prepare for ruby default switch to 3.4tb2025-06-271-4/+4
|
* sync anton's fix for OpenSSL 3.3 interop to 3.4tb2025-06-231-2/+2
|
* OpenSSL is linked against pthread by now; ok tb@anton2025-06-231-2/+2
|
* tlsfuzzer: adjust test filenames to upstream churn.tb2025-06-151-154/+154
| | | | Requires py3-tlsfuzzer-20250516 to work
* ec_asn1_test: be better at sortingtb2025-06-141-3/+3
|
* ec_asn1_test: for curves that have a seed, validate the parameters a and btb2025-06-141-2/+195
| | | | | | per X9.62, F.3.4.b. This ensures that the table entries in ec_curves.c for the NIST curves P-224, P-256, P-384, and P-521 are internally consistent and in particular that the seed is correct.
* Add a test to verify the fpurge problem doesn't happen. fpurge()yasuoka2025-06-121-1/+41
| | | | | mistaknely made the write buffer usable even if the stream is read mode. See the change of lib/libc/stdio/fpurge.c,v 1.11.
* allow checking of tls.hschwarze2025-06-081-2/+3
|
* allow checking of conf.hschwarze2025-06-081-1/+5
|
* Test to verify the handling of fflush() for the pushed-back buffer thatyasuoka2025-06-081-1/+40
| | | | has been read or that has not.
* libtls: add basic regress for ALPNtb2025-06-041-1/+138
| | | | | This currently only tests the behavior for successful protocol negotiations since the test expects all handshakes to complete.
* Now our fflush() comply POSIX-2008. test_fflush is expected "pass".yasuoka2025-06-032-6/+3
| | | | And switch test___freadahead to use another version that uses fflush().
* parse_test_file: add a missing call to finish in last cleanuptb2025-06-031-1/+4
|
* parse_test_file: add missing error checks for init()tb2025-06-031-3/+5
|
* Add non-EVP tests for AES CFB128 and OFB128 modeskenjiro2025-06-031-8/+112
| | | | | | | | | Extend aes_test.c to include non-EVP tests for AES CFB128 and OFB128 modes using AES_cfb128_encrypt() and AES_ofb128_encrypt(). These additions improve test coverage by exercising the low-level interfaces with the same vectors used in the EVP-based tests. ok tb@
* openssl-ruby/Makefile: zap trailing whitespace added in previoustb2025-05-311-2/+2
|
* explicit_bzero test: don't redefine __SANITIZE_ADDRESS__tb2025-05-311-1/+3
| | | | Silences an annoying warning when running tests with ASAN.
* test.h: include stddef.h for NULL and size_ttb2025-05-311-1/+2
|
* test.c: drop include of libgen.htb2025-05-311-2/+1
| | | | | This no longer uses basenam, so we can drop this header which isn't available on Windows.
* test.c: plug leak of tmp_filetb2025-05-311-1/+2
|
* Fix attributes in test.htb2025-05-311-4/+4
| | | | | | | | | | The __attribute__ is part of the function declaration, hence drop the incorrect early semicolons. Fixes the build of the md test on sparc64. In file included from /usr/src/regress/lib/libcrypto/md/md_test.c:25: /usr/src/regress/lib/libcrypto/md/../test/test.h:61: warning: empty declaration /usr/src/regress/lib/libcrypto/md/../test/test.h:77: warning: empty declaration /usr/src/regress/lib/libcrypto/md/../test/test.h:114: warning: empty declaration
* test.c: avoid NULL-dereferencetb2025-05-311-2/+3
| | | | | | | test_init() calls test_new(NULL, NULL), which leads to a segfault. llvm 16 optimizes this away with -O2, however gcc 4.2.1 on sparc64 doesn't. Fix this by only inheriting the out FILE from the parent if the latter is non-NULL.
* Add test whether fflush() complies POSIX for the handling ofyasuoka2025-05-251-1/+82
| | | | pushed-back wchar_t chars.
* Add test for ungetwc().yasuoka2025-05-252-1/+94
|
* Add tests for the functions in <stdio_ext.h>.yasuoka2025-05-257-2/+455
|
* Include "stdio" in SUBDIR. This should have been done along with theyasuoka2025-05-251-4/+4
| | | | previous commit.
* Add regress/lib/libc/stdio/test_fflush.c to test fflush() behavior foryasuoka2025-05-242-0/+236
| | | | | | reading FILE objects. It will fail until fflush() complies POSIX-2008. ok tb asou
* Adapt to new maloc_options declarationotto2025-05-241-2/+2
|
* Adapt test to new malloc_options regimeotto2025-05-241-7/+8
|
* Add the ability to run individual ruby ssl test for figuring outbeck2025-05-231-1/+16
| | | | | | what is going on when these break ok tb@
* asn1: merge invalid generalized time tests into invalid time testsjoshua2025-05-221-16/+10
| | | | | | | | | | | Previously, invalid generalized time tests were split into a separate set of test vectors and a flag was used when calling the test function to indicate they should be tested as generalized only. This simplifies the code a bit, and makes converting to the new test framework easier. ok jsing
* Convert sha_test to use new test frameworkjoshua2025-05-222-153/+141
| | | | ok beck
* Convert md_test to use new test frameworkjoshua2025-05-222-122/+106
| | | | ok jsing tb beck
* Fix test_errorf macro expanding to two linesjoshua2025-05-221-4/+8
| | | | | This caused test_fail to always be called when used in certain conditions, and wrapping with do {} while (0) fixes this.
* Add basic HKDF test using EVP_PKEY_HKDFkenjiro2025-05-221-1/+81
| | | | | | | | Add a basic test case for HKDF using EVP_PKEY_HKDF to evp_test.c. This test verifies the correct derivation of output keying material using SHA-256, matching the test vector from RFC 5869 Appendix A.1. ok tb@ joshua@
* Add initial regress test frameworkjoshua2025-05-213-0/+408
| | | | | | | | | | Add a test framework for use in LibreSSL regression tests. This test framework aims to be as lightweight and as simple to use as possible. The design is mostly inspired by Go's test system, and aims to be a drop-in utility in most existing regress tests. ok jsing tb beck
* Add NULL checks to HKDF and TLS1-PRF EVP_PKEY cleanup functionskenjiro2025-05-211-1/+3
| | | | | | | | Check if ctx->data is NULL before calling freezero(). Also add HKDF and TLS1-PRF to the EVP_PKEY cleanup regression test, as they no longer crash with this change. ok tb@