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 1Pt7sp-0001aK-TK for garchives@archives.gentoo.org; Sat, 26 Feb 2011 00:19:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6C5DA1C06D for ; Sat, 26 Feb 2011 00:19:39 +0000 (UTC) Received: from mail-ww0-f41.google.com (mail-ww0-f41.google.com [74.125.82.41]) by pigeon.gentoo.org (Postfix) with ESMTP id 051721C053 for ; Sat, 26 Feb 2011 00:09:43 +0000 (UTC) Received: by wwb17 with SMTP id 17so1256700wwb.4 for ; Fri, 25 Feb 2011 16:09:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=MbyzwlM0LzWnX0TM+KcXL8mQo2jNqAUWF8jzsEoDUz0=; b=kPtgkOvA3VRs+AEoPBJFKu7kHGofrx9hBqdL1BQHP5N/R56tcc3Uv/CmAQiPlD6ok3 MTGNGwBS7xwaC10AIMkXWgANenesq84yg2zSWRbvDh50lw4nrTaGdq+oZD2AUQWQB0d6 /qerBq4l6dgxtB1PNd699vj7scUsL0eEqyWow= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=SjWldsFA9pfheKoKCriD79oNlKDLdsqqLKRF1ChEgBkbfHGQnQk9tkzXEHgh+SeiHY Wi+70LxggKIS+tP+o+h+NUOBN9tcC4qedjLvCdat8Rs0IcwObuIvYcH+YBRM+gOc3SuY JMOsn7HVZdMLqziVFy3wY2P7u6GY/5tz7DF2A= Received: by 10.227.30.31 with SMTP id s31mr2680500wbc.27.1298678983186; Fri, 25 Feb 2011 16:09:43 -0800 (PST) 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 Received: by 10.227.151.197 with HTTP; Fri, 25 Feb 2011 16:09:23 -0800 (PST) In-Reply-To: <4D63A165.4000007@optonline.net> References: <4D63A165.4000007@optonline.net> From: Mark Shields Date: Fri, 25 Feb 2011 19:09:23 -0500 Message-ID: Subject: Re: [gentoo-user] ssh problem To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=002215b026467859d4049d2443c6 X-Archives-Salt: X-Archives-Hash: bdf1487453d105e0c78a0d9c73a5daa6 --002215b026467859d4049d2443c6 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 22, 2011 at 6:43 AM, dhk wrote: > After a recent upgrade to ssh I can no longer log into my Gentoo box > (amd64) from another Gentoo box (x86) that has also had a recent upgrade > to ssh. However, I can log in to it from Suse and Redhat boxes. > > Any ideas? > > Thanks > > dhk > > While this may not help you now, one of the things Gentoo devs recommend, after updating the ssh daemon and restarting it, is to immediately try to ssh back in and make sure you still can. Do not close your original ssh connection when you do this. I've had these instructions save me a few times; since I was still connected, I was able to fix the sshd_config file. --002215b026467859d4049d2443c6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 22, 2011 at 6:43 AM, dhk <dhkuhl@optonline.net= > wrote:
After a recent upgrade to ssh I can no longer log into my Gentoo box
(amd64) from another Gentoo box (x86) that has also had a recent upgrade to ssh. =A0However, I can log in to it from Suse and Redhat boxes.

Any ideas?

Thanks

dhk


While this may not help you now, one of = the things Gentoo devs recommend, after updating the ssh daemon and restart= ing it, is to immediately try to ssh back in and make sure you still can. = =A0Do not close your original ssh connection when you do this. =A0

I've had these instructions save me a few times; si= nce I was still connected, I was able to fix the sshd_config file.
--002215b026467859d4049d2443c6--