Date: Sat, 29 Nov 2003 02:09:34 -0500 From: Steve Bertrand <iaccounts@northnetworks.ca> To: "Jerry M. Howell II" <jmhowell@jmhowell.com> Cc: freebsd-questions@freebsd.org Subject: Re: ssh issue Message-ID: <1070089773.13950.12.camel@ptp.northnetworks.ca> In-Reply-To: <20031128233522.A6417@jmhowell.com> References: <20031125183807.H13943@asu.edu> <20031128233522.A6417@jmhowell.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, Nov 25, 2003 at 06:38:07PM -0700, David Bear wrote: > > running 4.7-RELEASE.. I'm trying to setup ssh pubkey auth and its not > > working.. > > > > I put my pub key in ~/.ssh/authorized_keys from system A > > > > On system B edited /etc/ssh/sshd_config with > > ====================== > > PubkeyAuthentication yes > > AuthorizedKeysFile .ssh/authorized_keys > > PasswordAuthentication no > > ===================== > > > > I chmod'd my .ssh dir as 700 on system A and B. Then restart sshd on > > system B explicitly using -f /etc/ssh/sshd_config . Ok, it sounds like you are putting the 'config' on the server side, not the client. I hope I am assuming correctly. Here is a snip from my 'config' on my client side. Note that I have two entries. Depending which network I am connected to, most of the time I can connect just using the servers hostname, and other times, must type in the entire domain name. Having an entry using each connection method (ip, hostname or FQDN) is important: ---snip--- Host host.northnetworks.ca User steve Compression no Protocol 2 RSAAuthentication yes StrictHostKeyChecking no ForwardAgent yes ForwardX11 no IdentityFile /home/steve/.ssh/xxx_dsa Host host User steve Compression no Protocol 2 RSAAuthentication yes StrictHostKeyChecking no ForwardAgent yes ForwardX11 no IdentityFile /home/steve/.ssh/xxx_dsa ---/snip--- Here's another site you can have a quick look at: http://ww3.northnetworks.ca/docs/ssh_key_auth Steve > > > > the ssh'ing into system B I'm still prompted for a password. > > > > I'm lost. Any advice. > > There are 2 ways I know to do this and the following URL shows you haw > to do both. BTW, if the remote server disallows passwordless logins it > doesn't mater how hard you try. > > http://www-uxsup.csx.cam.ac.uk/pwf-linux/intro/remote.passwordless.html > > sure it's focused on linux but it'll work just the same on freeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1070089773.13950.12.camel>