-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Apr 1, 2007, at 1:56 AM, Dan Fandrich wrote:

> On Sat, Mar 31, 2007 at 10:32:28PM -0700, Dan Fandrich wrote:
>> On Sat, Mar 31, 2007 at 05:28:06PM -0400, Daniel Johnson wrote:
>>> I applied your patch to libssh2 HEAD and rebuilt it. I then ran
>>> testcurl.pl --nocvsup. It no longer hangs, but tests 600-603 all
>>> fail
>>> now. They all fail at the same point: "BSM audit:
>>> bsm_audit_session_setup: setaudit_addr failed: Operation not
>>> permitted". I've uploaded the build log to the autobuild server.
>>
>> I'm not sure exactly what "BSM audit" is all about...
>
> ...but I think I've figured out now, anyway. It looks like the
> bsm_audit_record failure message is a red herring. It's just a
> warning that
> the test harness sshd couldn't log the fact that curl logged in,
> because
> BSM logging requires root permission. I suspect this message will
> always
> appear in the ssh.log file when BSM auditing is enabled in sshd;
> it's just
> that you would only normally see it when the test fails.
>
> As for the cause of the failures--I'm not sure. There's another
> bug in
> libssh2 that sometimes causes test 603 failures for me, but that's not
> what's causing the other failures. Does it go away when you revert the
> libssh2 patch?

My ssh -V is "OpenSSH_4.5p1, OpenSSL 0.9.7l 28 Sep 2006".

If I revert the patch, it hangs. With the patch it fails as
previously noted. It also now fails with libssh2 0.14 where it used
to work.

Daniel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: http://homepage.mac.com/danielj7/publickey.txt

iD8DBQFGD8H04sDFGYouOqARAsi4AJ4+gTQCZ6etWZHcUgYW3gU7nuRp8gCfRfpO
wDWCbGWkfdYmtMQhZlIX1rE=
=nw8I
-----END PGP SIGNATURE-----
Received on 2007-04-01