authentication failures when using OpenSSH 2.9.9 or SunSSH.

Verified fact: Even when only using publickey authentication,
OpenSSH and SunSSH first validate the user, this implies that
if the user validation fails, 'invalid user', the publickey
authentication will not be allowed to complete.

failures when using OpenSSH 2.9.9 or SunSSH

later to accept 'none' as an indication to disable connection multiplexing

 ConnectTimeout
 ForwardX11Trusted
 HashKnownHosts
 RekeyLimit
 ServerAliveCountMax
 ServerAliveInterval

requires a non blank argument.

SCP, SFTP and SOCKS4 tests is now OpenSSH 2.9.9 or SunSSH 1.0

For SOCKS5 tests minimum versions are OpenSSH 3.7 or SunSSH 1.0

components doesn't have read permission set.

Cleanup some debugging messages. Unlink log file on exit.

the socks server port in the test suite. This is the default setting
unless a tinkered built ssh is being used.

of test suite ssh and socks servers.

Gather additional debug info when the test suite ssh server fails to start.

are good/compatible enough to run the test suite ssh server and
socks tests

when sshd is not being identified as an OpenSSH daemon

Improve wording of a couple of debug messages.

found or the OpenSSH version found

keys that small.

really reduce security since in the common case of a daily automated build
the keys are only used for a single test run lasting a few minutes before
being deleted.

sftp tests run fine on gentoo

Added more options to the ssh config file to improve the consistency of
the test environment.
Force a rewrite of the ssh config files on every invocation.
Changed the opens to work on older versions of perl.

openssh

Try to avoid this problem checking for some possible unsupported options,
and avoid using them in the configuration file.

in the PATH and afterwards in other common locations.