From owner-freebsd-stable@FreeBSD.ORG Fri Apr 2 10:59:27 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFECF16A4CE; Fri, 2 Apr 2004 10:59:27 -0800 (PST) Received: from fep03-mail.bloor.is.net.cable.rogers.com (fep03-mail.bloor.is.net.cable.rogers.com [66.185.86.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C40443D1D; Fri, 2 Apr 2004 10:59:27 -0800 (PST) (envelope-from desjardins@canada.com) Received: from gateway.lan.daren.ca ([65.49.123.132]) by fep03-mail.bloor.is.net.cable.rogers.comESMTP <20040402185907.CORQ396979.fep03-mail.bloor.is.net.cable.rogers.com@gateway.lan.daren.ca>; Fri, 2 Apr 2004 13:59:07 -0500 Received: from [216.130.212.41] (account daren@daren.ca HELO [216.130.212.41]) by gateway.lan.daren.ca (CommuniGate Pro SMTP 4.1.8) with ESMTP id 221044; Fri, 02 Apr 2004 13:59:25 -0500 From: Daren Desjardins To: Jonathon McKitrick In-Reply-To: <20040402164928.GA70822@dogma.freebsd-uk.eu.org> References: <20040221202305.GA78752@dogma.freebsd-uk.eu.org> <000e01c3f8bc$9ee42dc0$efe8fea9@unixsmith.com> <20040325023251.GA61864@dogma.freebsd-uk.eu.org> <20040325225859.GA22615@dogma.freebsd-uk.eu.org> <20040402160232.GB68803@dogma.freebsd-uk.eu.org> <20040402164928.GA70822@dogma.freebsd-uk.eu.org> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1080932364.343.6.camel@lithium.stabilia.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 02 Apr 2004 13:59:25 -0500 Content-Transfer-Encoding: quoted-printable X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep03-mail.bloor.is.net.cable.rogers.com from [65.49.123.132] using ID at Fri, 2 Apr 2004 13:59:07 -0500 cc: "Christian W. Sung" cc: Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= cc: freebsd-stable@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: ssh no longer connecting automatically X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2004 18:59:28 -0000 Ive been having the exact same issue, even started a thread on it with no resolution yet. Some findings I have made recently included taking a working ssh from a bsd4.9 release box, copying it to the one that wasnt working, including the config. That ssh also had the problem after copying. This seems to indicate either the config has issues(but I copied that as well) or a runtime library conflict... The code where it dies can be found in the source ssh-dss.c, at ' ret =3D DSA_do_verify(digest, dlen, sig, key->dsa);' I believe, line 172. On Fri, 2004-04-02 at 11:49, Jonathon McKitrick wrote: > On Fri, Apr 02, 2004 at 06:13:50PM +0200, Dag-Erling Sm=F8rgrav wrote: > : Jonathon McKitrick writes: > : > This might be a silly question, but is it possible that a problem wit= h my > : > local hostname could cause the key to somehow fail validation? > :=20 > : I don't think so. > :=20 > : I think I have managed to reproduce the problem, but I don't really > : have a clear idea of where in the source code to start looking for a > : solution. My current theory is that ssh somehow gets confused about > : what what kind of key it is handling, and tries to treat a DSA key as > : an RSA key (or vice versa). >=20 > Well, that's good. I was starting to wonder what was wrong with my home > setup. >=20 > Workaround? >=20 >=20 >=20 > jm