From owner-freebsd-stable Sun Jul 14 19:38: 8 2002 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 6BE6C37B400 for ; Sun, 14 Jul 2002 19:38:05 -0700 (PDT) Received: from aurora.siteplus.com (aurora.siteplus.com [66.129.2.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id C94FC43E6D for ; Sun, 14 Jul 2002 19:38:04 -0700 (PDT) (envelope-from jim@jwweeks.com) Received: from veager.jwweeks.com (pcp01076331pcs.midval01.tn.comcast.net [68.59.219.194]) by aurora.siteplus.com (8.12.5/8.12.5) with ESMTP id g6F2bwbc069219; Sun, 14 Jul 2002 22:37:58 -0400 (EDT) (envelope-from jim@jwweeks.com) Date: Sun, 14 Jul 2002 22:38:00 -0400 (EDT) From: Jim Weeks To: Gregory Bond Cc: freebsd-stable@FreeBSD.ORG, Subject: Re: ssh keys not accepted In-Reply-To: <200207150040.KAA27019@lightning.itga.com.au> Message-ID: <20020714222732.V526-100000@veager.jwweeks.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 15 Jul 2002, Gregory Bond wrote: > > For some strange reason, keys from this host are not accepted by any of my > > other machines. However, I can push id_dsa.pub into authorized_keys2 on > > this machine and login from any other host. > > Check that the authorised_keys2 file on the remote host has each key on > exactly 1 line. I sometimes get bitten by unnoticed linebreaks when > cut-n-pasting keys using xterm! > And, Andrew P. Lentvorski wrote: > Did you try using "ssh -2 " to force version 2 of the ssh > protocol to be used? The defaults in ssh_config and sshd_config > automatically set everything to version 1. The relevant line will say > "Protocol 1,2" when you probably want "Protocol 2,1". Thanks for all the replies ;-) Since the whole ssh update has been a hot topic, I am combining these two responses to save bandwidth. Both of these were good suggestions, but they weren't the solution. Evidently I missed something with this particular machine when I upgraded ssh. Any way, rebuilding ssh and pam did the trick. Regards, -- Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message