Hi Dan,
> Hmmm, good question; it should just work. The error your autobuild is
> "Authentication failure" which implies that the ssh server isn't set
> up correctly to authenticate using the public key generated by the test
> suite. What version of sshd do you have on that system? Maybe OpenSuSE
IIRC I installed a version from CVS around mid January 2007;
have just now updated with a recent version - perhaps this fixes ir already....

> has patched that sshd to disallow what the test suite is doing, or has
> changed some option from the default and it's not being set back by the
> test suite. I've added a couple more such options in CVS, but I don't
> know if there are any more.

> Do you have a non-empty file /etc/hosts.allow, /etc/hosts.deny,
> /etc/ssh/shosts.equiv, ~/.shosts, ~/.rhosts ? Does your sshd allow
> DSA keys? Do the generated files curl_*_key* files in the tests directory
> look correct? Are you running SELinux or other hardened infrastructure
> that might interfere somehow with sshd authentication?

> I've turned on an sshd option that allows debugging of its connections
> now.
> There may be clues in log/ssh.log file now as to why it's not
> authenticating.

it seems to me that its probably related to the cronjob user which runs the test...
see recent build log...

Guen.
Received on 2007-03-28