From owner-freebsd-questions Tue Jan 18 13:45:48 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 72D5F15296 for ; Tue, 18 Jan 2000 13:45:42 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id KAA47149; Wed, 19 Jan 2000 10:45:24 +1300 (NZDT) Message-Id: <200001182145.KAA47149@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: Roelof Osinga , "Crist J. Clark" , questions@FreeBSD.ORG Date: Wed, 19 Jan 2000 10:45:20 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: OpenSSH 1.2.1 refusing incoming connections Reply-To: dan@freebsddiary.org Cc: questions@FreeBSD.ORG, dan@freebsdzine.org In-reply-to: <3884DDAE.ECB9C583@nisser.com> X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the reply. I've tried the OpenBSD mailing lists, but Theo told me (privately) they cant help me as this is a FreeBSD issue. I don't know how he concluded that. On 18 Jan 00, at 22:39, Roelof Osinga wrote: > Too bad the ktrace doesn't log the function parameters. Perhaps > "ktrace -i -ti" does? Or a debug session? Or maybe it does, your > trace stopped short of the interesting stuff: I think the problem is that I ran ktrace as non-root. I did run it as root and received about 277 KB of output. I was about to supply a URL for that output, but someone on IRC mentioned it contained encrypted passwords. Not a nice thing to publicly distribute. > > > 39607 ktrace NAMI "/usr/games/ssh" > > 39607 ktrace RET execve -1 errno 2 No such file or directory > > 39607 ktrace CALL execve(0xbfbfd79c,0xbfbfdc60,0xbfbfdc6c) > > 39607 ktrace NAMI "/usr/local/bin/ssh" > > 39607 ktrace NAMI "/usr/libexec/ld-elf.so.1" > > All those execve errors refer to the system trying all dirs in your > PATH. The last one (NAMI "/usr/local/bin/ssh") succeeds. So at that > point ssh gets executed and your trace seemingly stops. > > Anyway, looks like the NAMI entries are the parameters after all . I think I should do another ktrace. And edit the output. I'll see what I can come up with. FWIW: on two boxes, both with FreeBSD 3.3-19991207-SNAP, one works, one doesn't with respect to sshd. Go figure. -- Dan Langille - DVL Software Limited [I'm looking for more work] The FreeBSD Diary - http://www.freebsddiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm unix @ home - http://www.unixathome.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message