summaryrefslogtreecommitdiff
path: root/src/regress/lib (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix ssltest to work with opaque EVP_PKEY.tb2021-11-181-22/+33
|
* sha*test: convert these tests to work with opaque EVP_MD_CTX.tb2021-11-183-31/+42
|
* zap trailing whitespacetb2021-11-181-7/+7
|
* hmactest: convert to opaque HMAC_CTX.tb2021-11-181-29/+37
|
* gost2814789t: convert to opaque EVP_{MD,CIPHER}_CTX.tb2021-11-181-19/+23
|
* exptest: convert to opaque BN; minor KNF tweaks.tb2021-11-181-40/+47
|
* evptest: fix compilation with opaque EVP_{CIPHER,MD}_CTX. Uses atb2021-11-181-22/+30
| | | | workaround for excessive malloc inspired by mariadb (just kidding).
* ecdsatest: make this test compile with opaque EVP_MD_CTX.tb2021-11-181-7/+8
|
* dsatest: make this work with opaque BN. Some more fixes will be neededtb2021-11-181-114/+124
| | | | | for opaque DSA. I'll deal with that later. I also lobbed a KNF grenade in here.
* dhtest: fix this to work with opaque BN. This will need more fixes totb2021-11-181-48/+61
| | | | | work with opaque DH, but one step at a time. While here, add a bunch of missing spaces to reduce the eyebleed.
* bntest: Fix all but one test in this file to work with opaque BN.tb2021-11-181-399/+563
| | | | | The remaining test needs some thinking (or disabling once we flip the switch). It is currently marked with an XXX.
* Test ASN1_STRING_copy(3).schwarze2021-11-132-1/+121
| | | | | | As a side effect, this also tests various aspects of ASN1_STRING_new(3), ASN1_STRING_set(3), ASN1_STRING_length_set(3), ASN1_STRING_get0_data(3), ASN1_STRING_length(3), and ASN1_STRING_type(3).
* Test adding extensions to certification requests.schwarze2021-11-032-2/+167
| | | | | Related to the bugfixes in x509_req.c rev. 1.25. OK tb@.
* Add regress that calls SSL_set_tlsext_host_name() with a NULL host name.jsing2021-11-021-1/+15
|
* Rework SNI hostname regress to be table driven.jsing2021-11-011-62/+147
| | | | | | | Also adjust for the changes to tlsext_sni_is_valid_hostname() and include tests for IPv4 and IPv6 literals. ok beck@
* Rework x509attribute regress test in such a way that it doesn't needtb2021-11-011-11/+7
| | | | to reach into opaque structs.
* Make this test compile again after the damage done in libcryptotb2021-10-311-19/+20
|
* Prepare regress for opaque structs in x509*.htb2021-10-314-25/+18
|
* openssl-ruby tests: rework for x509_alt.c r1.3 and r1.5.tb2021-10-281-6/+9
| | | | | | | ruby can no longer generate certs with bogus wildcards in it to check that they will fail to verify when creating TLS connections. It will throw an error. This change needs openssl-ruby-tests-20211024p0 or later to work.
* Free memory on text exit to make asan quieterbeck2021-10-261-53/+83
| | | | ok tb@
* Revise regress for removal of SSL_SESSION_INTERNAL.jsing2021-10-261-27/+27
|
* For open/openat, if the flags parameter does not contain O_CREAT, thederaadt2021-10-242-4/+4
| | | | | | | | | | | | | 3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert
* Add a regress test for TLS client/server.jsing2021-10-233-1/+496
| | | | | | | | | This currently exercises various combinations of TLS versions and their associated key exchange mechanisms. Note that this currently fails for TLSv1.0/TLSv1.1 with RSA KEX (to be fixed shortly). Over time all of the ssl regress should be moved into the dtls and tls regress tests.
* Revise regress test for tls13_buffer rename.jsing2021-10-231-14/+16
|
* Revise regress for tlsext_tick_lifetime_hint changing type.jsing2021-10-231-2/+2
|
* Pull in ssl_locl.h so that we can keep reaching into libssl internals.jsing2021-10-152-1/+4
|
* ssltest.c does not need param.htb2021-10-131-1/+0
| | | | From Jonas Termansen
* Remove __dead from usage() to reduce the diff needed to build LibreSSLtb2021-10-131-3/+3
| | | | | | on sortix. Prompted by a diff by Jonas Termansen
* Mark another test as failing with the legacy verifier.jsing2021-09-302-2/+4
| | | | | This test now fails with the legacy verifier, due to X509_V_FLAG_TRUSTED_FIRST being enabled by default.
* Remove recent changes used to unblock the signal undergoing testing, I solved itanton2021-09-282-30/+2
| | | | | by changing my regress environment instead. This reduces the delta to the NetBSD upstream.
* Mark "failures" volatile to avoid a problem with sigsetjmp/siglongjmp.millert2021-09-272-4/+4
| | | | | | This makes the test pass on sparc64 where the compiler may otherwise store the variable in the strlcpy/strlcat function's delay slot. OK kettenis@
* These tests pass in a few seconds. Remove REGRESS_SLOW_TARGETS.bluhm2021-09-271-3/+1
|
* Make t_gettimeofday pass on sparc64.mbuhl2021-09-271-1/+3
| | | | OK bluhm@
* Simplify runAesCmacTest() by using EVP_DigestSign().tb2021-09-241-16/+3
|
* At least t_fork and t_vfork tests need coredumps enabled to succeed.claudio2021-09-191-1/+2
| | | | | | Add ulimit -c unlimited before running the tests like it is done in other places in regress. OK bluhm@
* Ensure that the kill signal undergoing testing is not ignored.anton2021-09-091-1/+15
| | | | ok bluhm@
* Rework openssl-ruby-tests to run all passing tests first, thentb2021-09-091-4/+12
| | | | | | | | | | | run the one failing test as a separate regress test. This way, all regressions should be caught with REGRESS_FAIL_EARLY=yes or on bluhm's regress webpage. This needs an up-to-date openssl-ruby-tests package and an upcoming commit by beck in x509_verify.c to work. ok beck bluhm
* zap trailing whitespacetb2021-09-091-7/+7
|
* The default Ruby has switched to 3.0tb2021-09-061-2/+2
|
* Disable tests that don't work in bluhms regress framework.mbuhl2021-09-041-1/+7
|
* Implement a -h option that allows specifying a target host thattb2021-09-031-9/+13
| | | | will be passed to the test scripts.
* Now that the issue is fixed, enable test-extensions.pytb2021-09-031-6/+2
|
* Make Bob happy.bluhm2021-09-031-1/+5
|
* Call the callback on success in new verifier in a compatible waybeck2021-09-031-3/+1
| | | | | | | | | | | | | when we succeed with a chain, and ensure we do not call the callback twice when the caller doesn't expect it. A refactor of the end of the legacy verify code in x509_vfy is probably overdue, but this should be done based on a piece that works. the important bit here is this allows the perl regression tests in tree to pass. Changes the previously committed regress tests to test the success case callbacks to be known to pass. ok bluhm@ tb@
* Add -f to usagetb2021-09-021-2/+2
|
* Enable vfork syscall test. Disable SIGSTOP test as it is masked untilmbuhl2021-09-025-6/+45
| | | | | exec/exit with vfork. OK bluhm@
* Import more NetBSD system call regression tests.mbuhl2021-09-0217-50/+2350
| | | | OK bluhm@
* delete %n using test cases, which now intentionally faultderaadt2021-09-021-13/+1
| | | | spotted by anton
* remove manual fiddling with MALLOC_OPTIONS from libc regress testsjasper2021-09-015-20/+5
| | | | | | | these options should be set globally (sysctl) when running regress as opposed to having individual tests set it, barring a few specific exceptions. ok bluhm@
* Add a regression test to verify that we call the callback in the samebeck2021-09-013-4/+551
| | | | | | | | | order on success for both the legacy and the new verifier, This avoids problems as seen in perl's regression tests for some of the crazy things net:ssleay does. This is currently marked as expected to fail, it will be expected to succeed after a forthcoming commit from me.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-05 09:24:20 +0000