provided for bug report #1871269, fixed on Jan 14 2008 before the 7.18.0
release.

out what valgrind to run.

previously had a number of flaws, perhaps most notably when an application
fired up N transfers at once as then they wouldn't pipeline at all that
nicely as anyone would think... Test case 530 was also updated to take the
improved functionality into account.

by the spawned server itself unless it is actually alive

started check also that the process is actually alive, since they
could have died once the pidfile was written out

already worked for FTP:// URLs

locations search list.

new minimum SSH version support for SCP, SFTP and SOCKS tests.

Some verbosity which still remains, will go out before next release.

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

- Capability of running socks5 tests must be based on ssh daemon version
  and not on ssh client version.

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

(http://curl.haxx.se/bug/view.cgi?id=1850730) I wrote up test case 552. The
test is doing a 70K POST with a read callback and an ioctl callback over a
proxy requiring Digest auth. The test case code is more or less identical to
the test recipe code provided by Spacen Jasset (who submitted the bug report).

components doesn't have read permission set.

directory components doesn't have read permission set.

A failed attempt to repeat bug report #1850730 (ie the test works fine).