Increase keyscan timeout from default. On slow hosts 3 concurrent keyscans
can hit the default 5 second timeout, so increase to 15 seconds.

test security key host keys in addition to user keys

test FIDO2/U2F key types; ok markus@

skip security-key key types for tests until we have a dummy
U2F middleware to use.

The test sshd_config in in $OBJ.

Remove leftover debugging.

Generate all key supported key types and enable for keyscan test.

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

try all supported key types here; bz#2455 reported by Jakub Jelen

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

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

make test for pr 2354 explicit

test keyscan as well (test for pr 2354)

test security key host keys in addition to user keys

test FIDO2/U2F key types; ok markus@

skip security-key key types for tests until we have a dummy
U2F middleware to use.

The test sshd_config in in $OBJ.

Remove leftover debugging.

Generate all key supported key types and enable for keyscan test.

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

try all supported key types here; bz#2455 reported by Jakub Jelen

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

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

make test for pr 2354 explicit

test keyscan as well (test for pr 2354)

test FIDO2/U2F key types; ok markus@

skip security-key key types for tests until we have a dummy
U2F middleware to use.

The test sshd_config in in $OBJ.

Remove leftover debugging.

Generate all key supported key types and enable for keyscan test.

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

try all supported key types here; bz#2455 reported by Jakub Jelen

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

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

make test for pr 2354 explicit

test keyscan as well (test for pr 2354)

skip security-key key types for tests until we have a dummy
U2F middleware to use.

The test sshd_config in in $OBJ.

Remove leftover debugging.

Generate all key supported key types and enable for keyscan test.

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

try all supported key types here; bz#2455 reported by Jakub Jelen

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

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

make test for pr 2354 explicit

test keyscan as well (test for pr 2354)

The test sshd_config in in $OBJ.

Remove leftover debugging.

Generate all key supported key types and enable for keyscan test.

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

try all supported key types here; bz#2455 reported by Jakub Jelen

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

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

make test for pr 2354 explicit

test keyscan as well (test for pr 2354)

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

try all supported key types here; bz#2455 reported by Jakub Jelen

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

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

make test for pr 2354 explicit

test keyscan as well (test for pr 2354)