summaryrefslogtreecommitdiffstats
path: root/regress/usr.bin (follow)
Commit message (Collapse)AuthorAgeFilesLines
* cannot effectively test posix-rename extension after changes indjm2021-03-311-8/+10
| | | | feature advertisment.
* In HTML output, correctly render .Bd -unfilled in proportionally-spacedschwarze2021-03-301-1/+1
| | | | | | | | | | | font, rather than with the monospace font appropriate for .Bd -literal. This fixes a minibug reported by anton@. Implemented by no longer relying on the typical browser default of "pre { font-family: monospace }" but instead letting <pre> elements inherit the font family from their parent, then adding an explicit CSS .Li class only for those displays where the manual page author requested it by using the -literal option on the .Bd macro.
* Build options regress with -DLIBRESSL_INTERNAL.jsing2021-03-211-2/+2
| | | | | This is currently needed for DTLS1_2_VERSION, however it should be used here regardless.
* add a test for misc.c:argv_split(), currently failsdjm2021-03-193-2/+144
|
* splitdjm2021-03-195-151/+235
|
* Add TEST_SSH_MODULI_FILE variable to allow overriding of the moduli filedtucker2021-03-131-2/+7
| | | | used during the test run.
* Check for the existence of p5-IO-Socket-SSL by checking for its SSL.pmtb2021-03-111-3/+4
| | | | | | | instead of running pkg_add which may block due to its locking mechanism. Precise file to check for suggested by sthen ok kn deraadt on previous version
* Dedicated regress test for snmp(1) instead of semi-relying on snmpd(8)'smartijn2021-03-092-2/+1173
| | | | | | | regress for basic functionality. This regress covers quite a few usecases, but there's still plenty missing. feedback and OK bluhm@
* zap spades of trailing whitespacetb2021-02-261-266/+266
|
* remove this KEX fuzzer; it's awkward to use and doesn't play nicedjm2021-02-264-585/+1
| | | | | with popular fuzzing drivers like libfuzzer. AFAIK nobody has used it but me.
* s/PubkeyAcceptedKeyTypes/PubkeyAcceptedAlgorithms/djm2021-02-255-29/+29
|
* Rename pubkeyacceptedkeytypes to pubkeyacceptedalgorithms in test todtucker2021-02-241-13/+13
| | | | match change to config-dump output.
* mark test-inlabel-wildcard-cert-no-CA-client as an expected failuretb2021-02-181-1/+2
|
* Make sure puttygen is new enough to successfully run the PuTTY interopdtucker2021-02-171-10/+9
| | | | tests, otherwise skip them.
* Add x509 certificate validation regression testsjan2021-02-163-2/+242
| | | | | | | The validation tests are originaly createtd by Steffen Ullrich. OK tb@ No objection jsing@
* Roll back the hostname->uname change in rev 1.10. It turns outdtucker2021-02-051-3/+3
| | | | | | | uname -n doesn't do what we need for some platforms in portable, so we'll fix the original problem (that some other platforms don't have hostname at all) by providing wrapper function to implement it.
* hostname is not specified by POSIX but uname -n is, so use the latter fordtucker2021-02-051-3/+3
| | | | portability. Patch from Geert Hendrickx via github PR#208.
* add a SK_DUMMY_INTEGRATE define that allows the dummy security keydjm2021-01-301-0/+7
| | | | middleware to be directly linked; useful for writing fuzzers, etc.
* Fix long->int for convtime tests here too. Spotted by tobhe@.dtucker2021-01-181-17/+17
|
* Change types in convtime() unit test to int to match change its new type.dtucker2021-01-151-16/+27
| | | | | Add tests for boundary conditions and fix convtime to work up to INT_MAX. ok djm@
* Adjust kexfuzz to addr.c/addrmatch.c split.dtucker2021-01-091-2/+2
|
* Update unittests for addr.c/addrmatch.c split.dtucker2021-01-099-17/+18
|
* Adapt to replacement of sntrup4591761x25519-sha512@tinyssh.org withdjm2020-12-293-7/+9
| | | | | | sntrup761x25519-sha512@openssh.com. Also test sntrup761x25519-sha512@openssh.com in unittests/kex
* more detail for failing testsdjm2020-12-221-3/+3
|
* regress test for KnownHostsCommanddjm2020-12-222-4/+58
|
* Remove explicit rijndael-cbc@lysator.liu.se test since the cipher wasdtucker2020-12-211-2/+2
| | | | removed.
* Rename syntax test of the \O escape sequence (suppress output groffschwarze2020-12-216-26/+26
| | | | | | extension; mandoc only implements syntax checking but ignores the sequence) to please Bill Gates and didickman@: avoid path names that only differ by case, like o.in vs. O.in.
* adapt to API change in hostkeys_foreach()/load_hostkeys()djm2020-12-211-19/+72
|
* slightly tweak the jot regress tests to avoid file name clashes ontb2020-12-204-4/+4
| | | | case insensitive file systems.
* Remove echo headlines.bluhm2020-12-171-60/+1
|
* Remove echo headlines. Makefile cleanup.bluhm2020-12-161-13/+3
|
* Remove the expected failures on armv7. They do not match the currentbluhm2020-12-141-2/+2
| | | | | behavior anyway. The map stack flag does not work in some cases. So lastcomm(1) regress should fail.
* Check return value of mmap(2) correctly and set correct flags. Nowbluhm2020-11-071-4/+5
| | | | | mmap(2) actually returns non-stack memory and triggers a SIGSEGV due to MAP_STACK on i386.
* The GNU tbl(1) program contained in the groff package internallyschwarze2020-10-256-6/+6
| | | | | | | | | | | | | | | | | | uses roff(7) tabulator settings to implement tables, and it used to leak the changed tabulator settings from tables to the subsequent roff(7) code. In mandoc/tbl_term.c rev. 1.42 (June 17, 2017), code was added to be bug-compatible with groff. In commit d0e03cf6 (Oct 20, 2020), GNU tbl(1) changed behaviour to save the tabulator settings before starting a table and restore them afterwards. Adjust mandoc for compatibility. Since mandoc implements tables without using roff(7) tabulator settings, saving and restoring tabulator settings is not needed in mandoc. Simply deleting the code that changed tabulator settings by reverting tbl_term.c rev. 1.42 is sufficient in mandoc. Also adjust the desired output of the regression tests to match the new behaviour of both groff and mandoc.
* Treat \*[.T] in the same way as \*(.T rather than calling abort(3).schwarze2020-10-247-14/+21
| | | | | Bug found because the groff-current manual pages started using the variant form of this predefined string.
* In HTML output, avoid printing a newline right after <pre>schwarze2020-10-1610-97/+47
| | | | | | | | and right before </pre> because that resulted in vertical whitespace not requested by the manual page author. Formatting bug reported by Aman Verma <amanraoverma plus vim at gmail dot com> on discuss@.
* few more things needs match.c and addrmatch.c now that log.cdjm2020-10-163-3/+7
| | | | calls match_pattern_list()
* remove GlobalKnownHostsFile for this test after UpdateHostkeysdjm2020-10-071-2/+5
| | | | change
* add tests for PKG_CONFIG_SYSTEM_INCLUDE_PATHjasper2020-09-153-2/+24
|
* Element next-line scopes can nest. Consequently, even when closingschwarze2020-09-095-10/+34
| | | | | | | | one element next-line scope, the MAN_ELINE flag must not yet be cleared if the parent macro is another element macro having next-line scope, or an assertion failure is caused if all this is wrapped in another macro that has block next-line scope, for example .TP. Bug found in an afl run performed by Jan Schreiber <jes at posteo dot de>.
* adapt to SSH_SK_VERSION_MAJOR crankdjm2020-09-091-1/+1
|
* oops, i tripped over $Mdocdate$ again; so sync the date after the commitschwarze2020-09-031-1/+1
|
* Fix two issues with .po (page offset) formatting:schwarze2020-09-033-2/+53
| | | | | | | | | | | | 1. Truncate excessive offsets to a width reasonable in the context of manual pages instead of printing excessively long lines and sometimes causing assertion failures; found in an afl run performed by Jan Schreiber <jes at posteo dot de>. 2. Remember both the requested and the applied page offset; otherwise, subtracting an excessive width, then adding it again, would end up with an incorrectly large offset. While here, simplify the code by reverting the previous offset up front, and also add some comments to make the general ideas easier to understand.
* If .ti had an excessive argument, using it was attempted, in someschwarze2020-09-033-2/+49
| | | | | | | | cases resulting in an assertion failure. Instead, truncate the temporary indent to a width reasonable in a manual page. I found the issue in an afl run that was performed by Jan Schreiber <jes at posteo dot de>.
* Do not indent by SIZE_MAX/2 when .ce occurs inside explicit no-fill mode.schwarze2020-09-022-4/+20
| | | | | | | | While here, drop two unused arguments from the function term_field(); the related work was already done by term_fill() before this commit. I found the bug in an afl run that was performed by Jan Schreiber <jes at posteo dot de>.
* Ignore unreasonably large spacing modifiers in tbl layouts.schwarze2020-09-016-5/+121
| | | | | | 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().
* Add regress test case for make/varmodifiers.c r1.48tb2020-08-302-1/+20
| | | | (Fix :S with anchors and replacement)
* Ensure that address/mask mismatches are flagged at config-check time.dtucker2020-08-281-1/+13
| | | | ok djm@
* adapt to API changesdjm2020-08-272-6/+7
|
* dummy firmware needs to match API version numner crank (fordjm2020-08-271-1/+1
| | | | | verify-required resident keys) even though it doesn't implement this feature
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.