Date: Sun, 14 Jul 2002 22:38:00 -0400 (EDT) From: Jim Weeks <jim@jwweeks.com> To: Gregory Bond <gnb@itga.com.au> Cc: freebsd-stable@FreeBSD.ORG, <bsder@mail.allcaps.org> Subject: Re: ssh keys not accepted Message-ID: <20020714222732.V526-100000@veager.jwweeks.com> In-Reply-To: <200207150040.KAA27019@lightning.itga.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <foobar>" 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020714222732.V526-100000>