From owner-freebsd-stable@FreeBSD.ORG  Fri Apr  2 08:50:10 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 EB6B916A4CE; Fri,  2 Apr 2004 08:50:10 -0800 (PST)
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AC0CC43D2D; Fri,  2 Apr 2004 08:50:10 -0800 (PST)
	(envelope-from jcm@FreeBSD-uk.eu.org)
Received: from dogma.freebsd-uk.eu.org ([130.88.200.97])
	by serenity.mcc.ac.uk with esmtp (Exim 4.20)
	id 1B9RrF-000GI9-P1; Fri, 02 Apr 2004 17:49:29 +0100
Received: from dogma.freebsd-uk.eu.org (localhost [127.0.0.1])
	i32GnTuf070841;	Fri, 2 Apr 2004 17:49:29 +0100 (BST)
	(envelope-from jcm@dogma.freebsd-uk.eu.org)
Received: (from jcm@localhost)
	by dogma.freebsd-uk.eu.org (8.12.10/8.12.6/Submit) id i32GnStp070840;
	Fri, 2 Apr 2004 17:49:28 +0100 (BST)
Date: Fri, 2 Apr 2004 17:49:28 +0100
From: Jonathon McKitrick <jcm@FreeBSD-uk.eu.org>
To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no>
Message-ID: <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> <xzpd671ayqk.fsf@dwp.des.no>
	<20040325225859.GA22615@dogma.freebsd-uk.eu.org> <xzpisgsf11n.fsf@dwp.des.no>
	<20040402160232.GB68803@dogma.freebsd-uk.eu.org> <xzpu102pdc1.fsf@dwp.des.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <xzpu102pdc1.fsf@dwp.des.no>
User-Agent: Mutt/1.4i
X-Spam-Score: -4.9 (----)
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/)
	*1B9RrF-000GI9-P1*F8JPgqWKLNg*
cc: "Christian W. Sung" <Christian@UNIXsmith.com>
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
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2004 16:50:11 -0000

On Fri, Apr 02, 2004 at 06:13:50PM +0200, Dag-Erling Smørgrav wrote:
: Jonathon McKitrick <jcm@FreeBSD-uk.eu.org> writes:
: > This might be a silly question, but is it possible that a problem with my
: > local hostname could cause the key to somehow fail validation?
: 
: I don't think so.
: 
: 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).

Well, that's good.  I was starting to wonder what was wrong with my home
setup.

Workaround?



jm
-- 
My other computer is your Windows box.