File Manager

003 File Manager

Current Path: /usr/src/crypto/openssh/regress

usr / src / crypto / openssh / regress /

📁 ..
📄 Makefile(6.8 KB)
📄 README.regress(3.91 KB)
📄 addrmatch.sh(2.06 KB)
📄 agent-getpeereid.sh(1.13 KB)
📄 agent-pkcs11.sh(1.86 KB)
📄 agent-ptrace.sh(1.31 KB)
📄 agent-timeout.sh(928 B)
📄 agent.sh(2.96 KB)
📄 allow-deny-users.sh(1.45 KB)
📄 authinfo.sh(574 B)
📄 banner.sh(1.24 KB)
📄 broken-pipe.sh(281 B)
📄 brokenkeys.sh(462 B)
📄 cert-file.sh(5.25 KB)
📄 cert-hostkey.sh(10.34 KB)
📄 cert-userkey.sh(11.95 KB)
📄 cfginclude.sh(4.39 KB)
📄 cfgmatch.sh(3.5 KB)
📄 cfgmatchlisten.sh(6.34 KB)
📄 cfgparse.sh(2.17 KB)
📄 check-perm.c(4.33 KB)
📄 cipher-speed.sh(799 B)
📄 conch-ciphers.sh(796 B)
📄 connect-privsep.sh(1.02 KB)
📄 connect-uri.sh(816 B)
📄 connect.sh(222 B)
📄 dhgex.sh(1.47 KB)
📄 dsa_ssh2.prv(863 B)
📄 dsa_ssh2.pub(732 B)
📄 dynamic-forward.sh(1.48 KB)
📄 envpass.sh(1.54 KB)
📄 exit-status.sh(562 B)
📄 forcecommand.sh(1.1 KB)
📄 forward-control.sh(7.71 KB)
📄 forwarding.sh(4.22 KB)
📄 host-expand.sh(384 B)
📄 hostkey-agent.sh(1.6 KB)
📄 hostkey-rotate.sh(3.86 KB)
📄 integrity.sh(2.33 KB)
📄 kextype.sh(587 B)
📄 key-options.sh(3.22 KB)
📄 keygen-change.sh(581 B)
📄 keygen-convert.sh(1.08 KB)
📄 keygen-knownhosts.sh(6.42 KB)
📄 keygen-moduli.sh(702 B)
📄 keys-command.sh(2.39 KB)
📄 keyscan.sh(403 B)
📄 keytype.sh(1.84 KB)
📄 krl.sh(6.45 KB)
📄 limit-keytype.sh(3.65 KB)
📄 localcommand.sh(351 B)
📄 login-timeout.sh(588 B)
📁 misc
📄 mkdtemp.c(1.53 KB)
📄 modpipe.c(3.81 KB)
📄 moduli.in(1.59 KB)
📄 multiplex.sh(7.09 KB)
📄 multipubkey.sh(2.31 KB)
📄 netcat.c(39.92 KB)
📄 portnum.sh(624 B)
📄 principals-command.sh(5.48 KB)
📄 proto-mismatch.sh(368 B)
📄 proto-version.sh(527 B)
📄 proxy-connect.sh(624 B)
📄 putty-ciphers.sh(678 B)
📄 putty-kex.sh(553 B)
📄 putty-transfer.sh(1021 B)
📄 reconfigure.sh(855 B)
📄 reexec.sh(878 B)
📄 rekey.sh(4.12 KB)
📄 rsa_openssh.prv(883 B)
📄 rsa_openssh.pub(213 B)
📄 rsa_ssh2.prv(924 B)
📄 scp-ssh-wrapper.sh(914 B)
📄 scp-uri.sh(2.01 KB)
📄 scp.sh(3.5 KB)
📄 setuid-allowed.c(1.45 KB)
📄 sftp-badcmds.sh(2.22 KB)
📄 sftp-batch.sh(1.16 KB)
📄 sftp-chroot.sh(845 B)
📄 sftp-cmds.sh(7.29 KB)
📄 sftp-glob.sh(2.47 KB)
📄 sftp-perm.sh(5.23 KB)
📄 sftp-uri.sh(1.59 KB)
📄 sftp.sh(737 B)
📄 ssh-com-client.sh(3.02 KB)
📄 ssh-com-keygen.sh(1.38 KB)
📄 ssh-com-sftp.sh(1.19 KB)
📄 ssh-com.sh(2.71 KB)
📄 ssh2putty.sh(693 B)
📄 sshcfgparse.sh(3.8 KB)
📄 sshd-log-wrapper.sh(285 B)
📄 stderr-after-eof.sh(603 B)
📄 stderr-data.sh(709 B)
📄 t11.ok(51 B)
📄 t4.ok(52 B)
📄 t5.ok(66 B)
📄 test-exec.sh(13.05 KB)
📄 transfer.sh(583 B)
📄 try-ciphers.sh(715 B)
📁 unittests
📄 valgrind-unit.sh(610 B)
📄 yes-head.sh(401 B)

Editing: README.regress

Overview.

$ ./configure && make tests

You'll see some progress info. A failure will cause either the make to
abort or the driver script to report a "FATAL" failure.

The test consists of 2 parts. The first is the file-based tests which is
driven by the Makefile, and the second is a set of network or proxycommand
based tests, which are driven by a driver script (test-exec.sh) which is
called multiple times by the Makefile.

Failures in the first part will cause the Makefile to return an error.
Failures in the second part will print a "FATAL" message for the failed
test and continue.

OpenBSD has a system-wide regression test suite. OpenSSH Portable's test
suite is based on OpenBSD's with modifications.

Environment variables.

SKIP_UNIT: Skip unit tests.
SUDO: path to sudo/doas command, if desired. Note that some systems
	(notably systems using PAM) require sudo to execute some tests.
LTESTS: Whitespace separated list of tests (filenames without the .sh
	extension) to run.
OBJ: used by test scripts to access build dir.
TEST_SHELL: shell used for running the test scripts.
TEST_SSH_FAIL_FATAL: set to "yes" to make any failure abort the test
	currently in progress.
TEST_SSH_PORT: TCP port to be used for the listening tests.
TEST_SSH_QUIET: set to "yes" to suppress non-fatal output.
TEST_SSH_SSHD_CONFOPTS: Configuration directives to be added to sshd_config
	before running each test.
TEST_SSH_SSH_CONFOPTS: Configuration directives to be added to
	ssh_config before running each test.
TEST_SSH_TRACE: set to "yes" for verbose output from tests 
TEST_SSH_x: path to "ssh" command under test, where x is one of
	SSH, SSHD, SSHAGENT, SSHADD, SSHKEYGEN, SSHKEYSCAN, SFTP or
	SFTPSERVER
USE_VALGRIND: Run the tests under valgrind memory checker.

Individual tests.

You can run an individual test from the top-level Makefile, eg:
$ make tests LTESTS=agent-timeout

If you need to manipulate the environment more you can invoke test-exec.sh
directly if you set up the path to find the binaries under test and the
test scripts themselves, for example:

$ cd regress
$ PATH=`pwd`/..:$PATH:. TEST_SHELL=/bin/sh sh test-exec.sh `pwd` \
    agent-timeout.sh
ok agent timeout test

Files.

test-exec.sh: the main test driver. Sets environment, creates config files
and keys and runs the specified test.

At the time of writing, the individual tests are:
agent-timeout.sh:	agent timeout test
agent.sh:		simple agent test
broken-pipe.sh:		broken pipe test
connect-privsep.sh:	proxy connect with privsep
connect.sh:		simple connect
exit-status.sh:		remote exit status
forwarding.sh:		local and remote forwarding
keygen-change.sh:	change passphrase for key
keyscan.sh:		keyscan
proto-mismatch.sh:	protocol version mismatch
proto-version.sh:	sshd version with different protocol combinations
proxy-connect.sh:	proxy connect
sftp.sh:		basic sftp put/get
ssh-com-client.sh:	connect with ssh.com client
ssh-com-keygen.sh:	ssh.com key import
ssh-com-sftp.sh:	basic sftp put/get with ssh.com server
ssh-com.sh:		connect to ssh.com server
stderr-after-eof.sh:	stderr data after eof
stderr-data.sh:		stderr data transfer
transfer.sh:		transfer data
try-ciphers.sh:		try ciphers
yes-head.sh:		yes pipe head

Problems?

Run the failing test with shell tracing (-x) turned on:
$ PATH=`pwd`/..:$PATH:. sh -x test-exec.sh `pwd` agent-timeout.sh

Failed tests can be difficult to diagnose. Suggestions:
- run the individual test via ./test-exec.sh `pwd` [testname]
- set LogLevel to VERBOSE in test-exec.sh and enable syslogging of
  auth.debug (eg to /var/log/authlog).

Known Issues.

- Similarly, if you do not have "scp" in your system's $PATH then the
  multiplex scp tests will fail (since the system's shell startup scripts
  will determine where the shell started by sshd will look for scp).

- Recent GNU coreutils deprecate "head -[n]": this will cause the yes-head
  test to fail.  The old behaviour can be restored by setting (and
  exporting) _POSIX2_VERSION=199209 before running the tests.

003 File Manager

Editing: README.regress

Upload File

Create Folder