summaryrefslogtreecommitdiff
path: root/regress
AgeCommit message (Collapse)Author
2020-09-01Ignore unreasonably large spacing modifiers in tbl layouts.Ingo Schwarze
Jan Schreiber <jes at posteo dot de> ran afl on mandoc and it turned out mandoc tried to use spacing modifiers so large that they would trigger assertion failures in term_ascii.c, function locale_advance().
2020-08-30Allow multiple global options.tobhe
2020-08-30Add regress test case for make/varmodifiers.c r1.48Theo Buehler
(Fix :S with anchors and replacement)
2020-08-29Add 'enforcesingleikesa' test.tobhe
2020-08-28Ensure that address/mask mismatches are flagged at config-check time.Darren Tucker
ok djm@
2020-08-27adapt to API changesDamien Miller
2020-08-27dummy firmware needs to match API version numner crank (forDamien Miller
verify-required resident keys) even though it doesn't implement this feature
2020-08-21Fix rpki-client regressTheo Buehler
The fix for the misuse of EVP_PKEY_cmp() (rpki-client/cert.c -r1.16) came with an API change. ta_parse() will now throw an error if fed a NULL pubkey. This in turn broke a regress test. Fix this by parsing the pubkey out of the appropriate TAL to let ta_parse() verify that it matches the pubkey in the first level certificate. Discussed with tobhe, benno and claudio
2020-08-18Fix bug in the select() portion of the test, the timeout was ignored.Todd C. Miller
The select() results are now consistent with what poll() returns.
2020-08-17Fix append mode so it always writes to the end and expand regress.Todd C. Miller
OK deraadt@ martijn@
2020-08-17Also print a list of missing scripts in summaryTheo Buehler
2020-08-17Avoid test failures due to outdated packagesTheo Buehler
Indicate missing test scripts prominently in the result but do not count them as an error.
2020-08-15enable jsing's zero content type testTheo Buehler
2020-08-11I accidentally zeored out a few bytes of the TLSv1.0 session ID.Theo Buehler
Restore them to their previous values.
2020-08-09Update TLS versions to match TLSv1.3 being enabled for TLS_method().Joel Sing
2020-08-09Fix regress test so that it exits non-zero for failure cases.Joel Sing
2020-08-09Update golden values to match P-521 being enabled by default in the client.Joel Sing
Diff from tb@
2020-08-09Update golden values to match P-521 being enabled by default in the client.Joel Sing
2020-08-08Add regression test for snmp(1) UTF-8 support by abusing the oid keywordMartijn van Duren
for usmUserSecurityName. This test will likely have to be adjusted once snmpd has genuine support for this object.
2020-08-08Session resumption is not currently supported for TLSv1.3.Theo Buehler
2020-08-08Enable P-521 and run the tests that use it.Theo Buehler
2020-08-03Put the code handling \} into a new function roff_cond_checkend()Ingo Schwarze
and call that function not only from both places where copies existed - when processing text lines and when processing request/macro lines in conditional block scope - but also when closing a macro definition request, such that this construction works: .if n \{.de macroname macro content .. \} ignored arguments .macroname This fixes a bug reported by John Gardner <gardnerjohng at gmail dot com>. While here, avoid a confusing decrement of the line scope counter in roffnode_cleanscope() for conditional blocks that do not have line scope in the first place (no functional change for this part). Also improve validation of an internal invariant in roff_cblock() and polish some comments.
2020-08-01Replace hostname underscore with hyphen in appstest.shKinichiro Inoguchi
2020-08-01add kcov remote coverage testsanton
2020-07-30bluhm@ has been pointing out for a long time that the mandoc test suiteIngo Schwarze
was quite nasty in hiding most of the commands being run with '@', hindering debugging in case anything failed. In particular, it hindered debugging that had to start from the log of a bulk regress run. So, finally, resolve this issue by removing almost all these '@'s. This commit does not change any of the test commands. If you want to be sure that you don't miss failures, run something like: make regress 2>&1 | tee make.log ; grep -B1 FAILED make.log
2020-07-27Add unveil test to lastcomm regress.rob
ok bluhm@
2020-07-26print the address of the "non-MAP_STACK stack", so it can be comparedTheo de Raadt
against failure reported in dmesg (hmm, is it time to delete those fault messages?)
2020-07-25Add stackpivot asm for ppc and ppc64 regress test.mortimer
Also tweak the pagefault test to work better on arches that do not modify the stack pointer on return.
2020-07-25With "%lx" new awk(1) prints 64 bit value also on 32 bit platforms.Alexander Bluhm
Replace it with Perl pack() to get hex representation of -1 on current platform. Make test pass again on i386.
2020-07-24If KTRACE environment is set, generate ktrace output also for clientAlexander Bluhm
and server. Together with the syslogd ktrace this helps debugging.
2020-07-24With TLS 1.3 error message has slightly changed if the cafile doesAlexander Bluhm
not contain the CA of the server certificate.
2020-07-24LibreSSL default TLS version has changed from 1.2 to 1.3. AdaptAlexander Bluhm
tests that use and check selected SSL version.
2020-07-23Fix a bug in PEM_X509_INFO_read_bio(3) that is very likely to causeIngo Schwarze
use-after-free and double-free issues in calling programs. The bug was introduced in SSLeay-0.6.0 released on June 21, 1996 and has been present since OpenBSD 2.4. I found the bug while documenting the function. The bug could bite in two ways that looked quite different from the perspective of the calling code: * If a stack was passed in that already contained some X509_INFO objects and an error occurred, all the objects passed in would be freed, but without removing the freed pointers from the stack, so the calling code would probable continue to access the freed pointers and eventually free them a second time. * If the input BIO contained at least two valid PEM objects followed by at least one PEM object causing an error, at least one freed pointer would be put onto the stack, even though the function would return NULL rather than the stack. But the calling code would still have a pointer to the stack, so it would be likely to access the new bogus pointers sooner or later. Fix all this by remembering the size of the input stack on entry and cutting it back to exactly that size when exiting due to an error, but no further. While here, do some related cleanup: * Garbage collect the automatic variables "error" and "i" which were only used at one single place each. * Use NULL rather than 0 for pointers. I like bugfixes that make the code four lines shorter, reduce the number of variables by one, reduce the number of brace-blocks by one, reduce the number if if-statements by one, and reduce the number of else-clauses by one. Tweaks and OK tb@.
2020-07-21trivial adjustment of the desired test resultsIngo Schwarze
after getting rid of the "copyless" crutch
2020-07-21adjust test framework to not require a ttyIngo Schwarze
2020-07-21Add pf config to block unencrypted pings.tobhe
2020-07-21Make test work with IPv6 addresses.tobhe
2020-07-20Improve MACHINE/MACHINE_ARCH access to actually testing architecturesTheo de Raadt
2020-07-20test _exit(2) rather than exit(3) [to keep things simpler], andTheo de Raadt
print the stack address [for comparison in dmesg post-fault]
2020-07-17Add test for '%k' (HostKeyAlias) TOKEN.Darren Tucker
2020-07-17Add tests for expansions on UserKnownHostsFile.Darren Tucker
2020-07-16Fix perl bugs that had me printing the wrong cert number for errorsBob Beck
2020-07-15Fix previous by calling the correct function.Darren Tucker
2020-07-15Update test to match recent change in match.cDarren Tucker
2020-07-15Use $OBJ to find key files. Fixes test when run on an obj directoryDarren Tucker
(on OpenBSD) or out of tree (in Portable).
2020-07-15The exit code from the perl matters hereBob Beck
2020-07-15Don't leak the X509_STOREBob Beck
2020-07-15Add certificate validation tests generated using the tools fromBob Beck
bettertls.com, and a verification suite to try each certificate in the same manner as the web based tests do using X509_verify. This includes the list of "known" failures today in our validaion code so we can move forward without moving back.
2020-07-14Enter the certs regress directory.Joel Sing
2020-07-14Add regress for X509_verify() using the new bundles.Joel Sing
A number of these tests are known to fail due to bugs/incorrect verification implementation.
generated by cgit v1.2.3 (git 2.25.1) at 2025-01-18 01:39:38 +0000