From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PsjKu-0008C1-FE for garchives@archives.gentoo.org; Thu, 24 Feb 2011 22:07:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DEF0C1C012 for ; Thu, 24 Feb 2011 22:06:59 +0000 (UTC) Received: from mta2.srv.hcvlny.cv.net (mta2.srv.hcvlny.cv.net [167.206.4.197]) by pigeon.gentoo.org (Postfix) with ESMTP id 0CAB6E0517 for ; Thu, 24 Feb 2011 21:52:08 +0000 (UTC) Received: from [192.168.0.4] (ool-43505ef2.dyn.optonline.net [67.80.94.242]) by mta2.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0LH5004NX62TTC70@mta2.srv.hcvlny.cv.net> for gentoo-user@lists.gentoo.org; Thu, 24 Feb 2011 16:52:07 -0500 (EST) Date: Thu, 24 Feb 2011 16:51:56 -0500 From: dhk Subject: Re: [gentoo-user] ssh problem In-reply-to: <201102241201.12178.matt@deploylinux.net> Cc: gentoo-user@lists.gentoo.org Message-id: <4D66D2FC.1010003@optonline.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Enigmail-Version: 1.1.2 References: <4D63A165.4000007@optonline.net> <4D669ED2.2060108@optonline.net> <201102241201.12178.matt@deploylinux.net> User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20110105 Lightning/1.0b3pre Thunderbird/3.1.7 X-Archives-Salt: X-Archives-Hash: 75890ab47321de4908f04d7fc6cecbd9 On 02/24/2011 03:01 PM, Matthew Marlowe wrote: > On Thursday, February 24, 2011 10:09:22 am dhk wrote: >>>> >>>> I still haven't gotten this to work. Am I the only one using this? The >>>> "ssh -i .ssh/id_dsa.pub host" didn't work. I get a message "Read from >>>> socket failed: Connection reset by peer" with or without the -i option. >>>> > > I encountered a similar, if not the same, problem this morning. > Upgraded SSH, rebooted server, and no longer able to login. Logs showed > errors I had not seen before. > > I managed to solve the problem when I noticed that ssh'ing to the fqdn of the > server failed, but ssh'ing to the server hostname worked. This implied there > might be an issue with the known_hosts file, so I blew away that on both the > client and server and all was well. > > I'm guessing the upgrade modified the default ssh host keys, the new code > somehow doesn't give the normal error about discrepencies in known_hosts, and > consequently although ones user keys are still fine, it fails. The issue here > is really the new error isn't nearly as understandable as the old. > > Anyhow, try it and I hope it works. > > Matt Thanks, but I've tried that. ssh'ing to the hostname and loopback address work. However, when I go out to the WAN it doesn't. So I can't ssh user@123.123.123.123 even though I have port 22 open on the switch for my ip.