Rework logging for the regression tests. Previously we would log to
ssh.log and sshd.log, but that is insufficient for tests that have more
than one concurent ssh/sshd.

Instead, we'll log to separate datestamped files in a $OBJ/log/ and
leave a symlink at the previous location pointing at the most recent
instance with an entry in regress.log showing which files were created
at each point. This should be sufficient to reconstruct what happened
even for tests that use multiple instances of each program. If the test
fails, tar up all of the logs for later analysis.

This will let us also capture the output from some of the other tools
which was previously sent to /dev/null although most of those will be
in future commits.

s/PubkeyAcceptedKeyTypes/PubkeyAcceptedAlgorithms/

Use $OBJ to find key files. Fixes test when run on an obj directory
(on OpenBSD) or out of tree (in Portable).

regress test for ssh-add -d; ok dtucker@

unit tests for ForwardAgent=/path; from Eric Chiang

test FIDO2/U2F key types; ok markus@

Only add ssh-dss to allowed key types if it's supported by the binary.

Enable ssh-dss for the agent test. Disable it for the certificate
test.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.

s/PubkeyAcceptedKeyTypes/PubkeyAcceptedAlgorithms/

Use $OBJ to find key files. Fixes test when run on an obj directory
(on OpenBSD) or out of tree (in Portable).

regress test for ssh-add -d; ok dtucker@

unit tests for ForwardAgent=/path; from Eric Chiang

test FIDO2/U2F key types; ok markus@

Only add ssh-dss to allowed key types if it's supported by the binary.

Enable ssh-dss for the agent test. Disable it for the certificate
test.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.

Use $OBJ to find key files. Fixes test when run on an obj directory
(on OpenBSD) or out of tree (in Portable).

regress test for ssh-add -d; ok dtucker@

unit tests for ForwardAgent=/path; from Eric Chiang

test FIDO2/U2F key types; ok markus@

Only add ssh-dss to allowed key types if it's supported by the binary.

Enable ssh-dss for the agent test. Disable it for the certificate
test.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.

regress test for ssh-add -d; ok dtucker@

unit tests for ForwardAgent=/path; from Eric Chiang

test FIDO2/U2F key types; ok markus@

Only add ssh-dss to allowed key types if it's supported by the binary.

Enable ssh-dss for the agent test. Disable it for the certificate
test.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.

unit tests for ForwardAgent=/path; from Eric Chiang

test FIDO2/U2F key types; ok markus@

Only add ssh-dss to allowed key types if it's supported by the binary.

Enable ssh-dss for the agent test. Disable it for the certificate
test.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.

test FIDO2/U2F key types; ok markus@

Only add ssh-dss to allowed key types if it's supported by the binary.

Enable ssh-dss for the agent test. Disable it for the certificate
test.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.

Only add ssh-dss to allowed key types if it's supported by the binary.

Enable ssh-dss for the agent test. Disable it for the certificate
test.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.

Enable ssh-dss for the agent test. Disable it for the certificate
test.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.

explicitly test all key types and their certificate counterparts

refactor a little

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

keep return values that are printed in error messages;
from portable

test ed25519 support; from djm@

replace 'echo -n' with 'printf' since it's more portable

more existant -> existent, from Martynas Venckus;
pfctl changes: ok henning
ssh changes: ok deraadt

allow specification of binary-under-test with
$TEST_SSH_{SSH,SSHD,SSHAGENT,SSHADD,SSHKEYGEN,SSHKEYSCAN}

try agent forwarding, too.

$OpenBSD$, public domain

we don't need a listening sshd for most of our tests, just
connect client and server w/o TCP:
ssh -o 'proxycommand sshd -i -f $OBJ/sshd_proxy'

delete agent keys, too

serveral tests for ssh-keygen/ssh/sshd/ssh-add/ssh-agent

note that these tests will start sshd on 127.0.0.1:4242
and will fail if the realpath of /usr/src/usr.sbin/ssh/obj/ contains
a group or world writeable directory.