• Home
Name Date Size #Lines LOC

..--

misc/03-May-2024-576483

unittests/03-May-2024-7,3366,204

MakefileD03-May-20246.6 KiB234188

README.regressD03-May-20243.7 KiB10578

addrmatch.shD03-May-20242.1 KiB5746

agent-getpeereid.shD03-May-20241.1 KiB5745

agent-pkcs11.shD03-May-20241.9 KiB7254

agent-ptrace.shD03-May-20241.3 KiB6755

agent-timeout.shD03-May-2024928 3730

agent.shD03-May-20242 KiB8268

allow-deny-users.shD03-May-20241.2 KiB4129

banner.shD03-May-20241.2 KiB4532

broken-pipe.shD03-May-2024367 1611

brokenkeys.shD03-May-2024477 2412

cert-file.shD03-May-20245.6 KiB170122

cert-hostkey.shD03-May-202410.1 KiB315268

cert-userkey.shD03-May-202411.9 KiB391318

cfginclude.shD03-May-20244.4 KiB294202

cfgmatch.shD03-May-20243.8 KiB12898

cfgparse.shD03-May-20242.2 KiB7652

check-perm.cD03-May-20244.3 KiB206163

cipher-speed.shD03-May-20241.2 KiB5242

conch-ciphers.shD03-May-2024796 2919

connect-privsep.shD03-May-20241.2 KiB4230

connect.shD03-May-2024293 148

dhgex.shD03-May-20241.5 KiB6147

dsa_ssh2.prvD03-May-2024863 1514

dsa_ssh2.pubD03-May-2024732 1413

dynamic-forward.shD03-May-20241.5 KiB6050

envpass.shD03-May-20241.5 KiB6148

exit-status.shD03-May-2024677 2518

forcecommand.shD03-May-20241.3 KiB4533

forward-control.shD03-May-20245.4 KiB169143

forwarding.shD03-May-20244.6 KiB150124

host-expand.shD03-May-2024468 2012

hostkey-agent.shD03-May-20241.6 KiB5441

hostkey-rotate.shD03-May-20243.9 KiB11178

integrity.shD03-May-20242.3 KiB7559

kextype.shD03-May-2024587 2617

key-options.shD03-May-20241.9 KiB7256

keygen-change.shD03-May-2024639 2921

keygen-convert.shD03-May-20241.1 KiB3422

keygen-knownhosts.shD03-May-20245.8 KiB198132

keygen-moduli.shD03-May-2024702 1910

keys-command.shD03-May-20242.4 KiB8362

keyscan.shD03-May-2024459 2516

keytype.shD03-May-20241.9 KiB7462

krl.shD03-May-20245.7 KiB186144

limit-keytype.shD03-May-20243.6 KiB9868

localcommand.shD03-May-2024398 1610

login-timeout.shD03-May-2024947 3324

modpipe.cD03-May-20243.8 KiB151123

moduli.inD03-May-20241.6 KiB43

multiplex.shD03-May-20247.1 KiB191153

multipubkey.shD03-May-20242.3 KiB6742

netcat.cD03-May-202439.8 KiB1,6601,293

portnum.shD03-May-2024624 3527

principals-command.shD03-May-20245.5 KiB169130

proto-mismatch.shD03-May-2024473 2216

proto-version.shD03-May-2024676 3730

proxy-connect.shD03-May-2024973 3325

putty-ciphers.shD03-May-2024692 2719

putty-kex.shD03-May-2024546 2315

putty-transfer.shD03-May-20241.1 KiB4233

reconfigure.shD03-May-2024996 4834

reexec.shD03-May-20241.1 KiB7145

rekey.shD03-May-20244.1 KiB173150

rsa_openssh.prvD03-May-2024883 1615

rsa_openssh.pubD03-May-2024213 21

rsa_ssh2.prvD03-May-2024924 1716

scp-ssh-wrapper.shD03-May-2024914 6051

scp.shD03-May-20243.5 KiB127101

setuid-allowed.cD03-May-20241.4 KiB5831

sftp-badcmds.shD03-May-20242.2 KiB6650

sftp-batch.shD03-May-20241.2 KiB5638

sftp-chroot.shD03-May-2024840 3221

sftp-cmds.shD03-May-20247.3 KiB233174

sftp-glob.shD03-May-20242.5 KiB7663

sftp-perm.shD03-May-20245.2 KiB270217

sftp.shD03-May-2024758 3326

ssh-com-client.shD03-May-20243 KiB131102

ssh-com-keygen.shD03-May-20241.4 KiB7564

ssh-com-sftp.shD03-May-20241.2 KiB6654

ssh-com.shD03-May-20242.7 KiB12095

ssh2putty.shD03-May-2024693 3524

sshcfgparse.shD03-May-20241.3 KiB3021

sshd-log-wrapper.shD03-May-2024285 123

stderr-after-eof.shD03-May-2024610 2517

stderr-data.shD03-May-2024758 3024

t11.okD03-May-202451 21

t4.okD03-May-202452 21

t5.okD03-May-202466 21

test-exec.shD03-May-202412.6 KiB581458

transfer.shD03-May-2024680 2721

try-ciphers.shD03-May-20241,017 4333

valgrind-unit.shD03-May-2024497 2113

yes-head.shD03-May-2024451 1611

README.regress

1Overview.
2
3$ ./configure && make tests
4
5You'll see some progress info. A failure will cause either the make to
6abort or the driver script to report a "FATAL" failure.
7
8The test consists of 2 parts. The first is the file-based tests which is
9driven by the Makefile, and the second is a set of network or proxycommand
10based tests, which are driven by a driver script (test-exec.sh) which is
11called multiple times by the Makefile.
12
13Failures in the first part will cause the Makefile to return an error.
14Failures in the second part will print a "FATAL" message for the failed
15test and continue.
16
17OpenBSD has a system-wide regression test suite. OpenSSH Portable's test
18suite is based on OpenBSD's with modifications.
19
20
21Environment variables.
22
23SUDO: path to sudo command, if desired. Note that some systems (notably
24	systems using PAM) require sudo to execute some tests.
25TEST_SSH_TRACE: set to "yes" for verbose output from tests
26TEST_SSH_QUIET: set to "yes" to suppress non-fatal output.
27TEST_SSH_x: path to "ssh" command under test, where x=SSH,SSHD,SSHAGENT,SSHADD
28	SSHKEYGEN,SSHKEYSCAN,SFTP,SFTPSERVER
29OBJ: used by test scripts to access build dir.
30TEST_SHELL: shell used for running the test scripts.
31TEST_SSH_PORT: TCP port to be used for the listening tests.
32TEST_SSH_SSH_CONFOPTS: Configuration directives to be added to ssh_config
33	before running each test.
34TEST_SSH_SSHD_CONFOPTS: Configuration directives to be added to sshd_config
35	before running each test.
36
37
38Individual tests.
39
40You can run an individual test from the top-level Makefile, eg:
41$ make tests LTESTS=agent-timeout
42
43If you need to manipulate the environment more you can invoke test-exec.sh
44directly if you set up the path to find the binaries under test and the
45test scripts themselves, for example:
46
47$ cd regress
48$ PATH=`pwd`/..:$PATH:. TEST_SHELL=/bin/sh sh test-exec.sh `pwd` \
49    agent-timeout.sh
50ok agent timeout test
51
52
53Files.
54
55test-exec.sh: the main test driver. Sets environment, creates config files
56and keys and runs the specified test.
57
58At the time of writing, the individual tests are:
59agent-timeout.sh:	agent timeout test
60agent.sh:		simple agent test
61broken-pipe.sh:		broken pipe test
62connect-privsep.sh:	proxy connect with privsep
63connect.sh:		simple connect
64exit-status.sh:		remote exit status
65forwarding.sh:		local and remote forwarding
66keygen-change.sh:	change passphrase for key
67keyscan.sh:		keyscan
68proto-mismatch.sh:	protocol version mismatch
69proto-version.sh:	sshd version with different protocol combinations
70proxy-connect.sh:	proxy connect
71sftp.sh:		basic sftp put/get
72ssh-com-client.sh:	connect with ssh.com client
73ssh-com-keygen.sh:	ssh.com key import
74ssh-com-sftp.sh:	basic sftp put/get with ssh.com server
75ssh-com.sh:		connect to ssh.com server
76stderr-after-eof.sh:	stderr data after eof
77stderr-data.sh:		stderr data transfer
78transfer.sh:		transfer data
79try-ciphers.sh:		try ciphers
80yes-head.sh:		yes pipe head
81
82
83Problems?
84
85Run the failing test with shell tracing (-x) turned on:
86$ PATH=`pwd`/..:$PATH:. sh -x test-exec.sh `pwd` agent-timeout.sh
87
88Failed tests can be difficult to diagnose. Suggestions:
89- run the individual test via ./test-exec.sh `pwd` [testname]
90- set LogLevel to VERBOSE in test-exec.sh and enable syslogging of
91  auth.debug (eg to /var/log/authlog).
92
93
94Known Issues.
95
96- Similarly, if you do not have "scp" in your system's $PATH then the
97  multiplex scp tests will fail (since the system's shell startup scripts
98  will determine where the shell started by sshd will look for scp).
99
100- Recent GNU coreutils deprecate "head -[n]": this will cause the yes-head
101  test to fail.  The old behaviour can be restored by setting (and
102  exporting) _POSIX2_VERSION=199209 before running the tests.
103
104$Id: README.regress,v 1.12 2011/05/05 03:48:42 djm Exp $
105