From owner-freebsd-amd64@FreeBSD.ORG  Sun Mar 27 18:35:49 2005
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0635316A4CE
	for <freebsd-amd64@freebsd.org>; Sun, 27 Mar 2005 18:35:49 +0000 (GMT)
Received: from april.chuckr.org (april.chuckr.org [66.92.151.30])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8759143D2F
	for <freebsd-amd64@freebsd.org>; Sun, 27 Mar 2005 18:35:48 +0000 (GMT)
	(envelope-from chuckr@chuckr.org)
Received: from [66.92.151.195] (july.chuckr.org [66.92.151.195])
	by april.chuckr.org (Postfix) with ESMTP
	id 7342111F96; Sun, 27 Mar 2005 13:33:54 -0500 (EST)
Message-ID: <4246FC58.3050005@chuckr.org>
Date: Sun, 27 Mar 2005 18:32:56 +0000
From: Chuck Robey <chuckr@chuckr.org>
User-Agent: Mozilla Thunderbird 1.0 (X11/20050316)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Hopkins <michael.hopkins@hopkins-research.com>
References: <BE6BCB92.36660%michael.hopkins@hopkins-research.com>
In-Reply-To: <BE6BCB92.36660%michael.hopkins@hopkins-research.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: "freebsd-amd64@freebsd.org" <freebsd-amd64@freebsd.org>
Subject: Re: SSH login issue
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2005 18:35:49 -0000

Michael Hopkins wrote:
> 
> Hi all
> 
> Anyone know why this is happening when I remotely ssh in to a 5.3p5 amd64
> server called Athlon?
> 
>  reverse mapping checking getaddrinfo for athlon failed - POSSIBLE BREAKIN
>  ATTEMPT!
> 
> It lets me in fine after I supply the password.

ssh caches info on the servers that you connect to, and stores that info 
in ~/.ssh/known_hosts, so if you're getting that message, and you decide 
that there's no security problem (ssh giving you a false alarm) then 
just take your favorite editor onto that file, and edit out the lines 
that refer to the server.  It hasn't got any sensitivity to "Athlon" 
built in, but it's trying to help you out and tell you about servers 
that have info that changes alarmingly.

> 
> TIA 
> 
> Michael
> 
> 
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> 
>         _/    _/   _/_/_/             Hopkins Research Ltd
>        _/    _/   _/    _/
>       _/_/_/_/   _/_/_/          http://www.hopkins-research.com/
>      _/    _/   _/   _/
>     _/    _/   _/     _/               'touch the future'
>                    
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> 
> 
> _______________________________________________
> freebsd-amd64@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"