Date: Mon, 27 Nov 2000 19:58:16 -0600 (CST) From: Mike Meyer <mwm@mired.org> To: tayers@bridge.com Cc: questions@freebsd.org Subject: Re: Help Understanding SSH Message-ID: <14883.4408.235484.60031@guru.mired.org> In-Reply-To: <52357945@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, I was hoping someone who had more experience with ssh would get to this one, but it hasn't happened. Take the following with more salt than usual. tayers@bridge.com types: > The first time I ran 'ssh B' on host A I got the following: > The authenticity of host 'B' can't be established. > RSA key fingerprint is xx:xx:xx:.... > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'B' (RSA) to the list of known hosts. > Enter passphrase for RSA key 'tayers@A.foo.net': This is normal the first time you connect to a host. SSH keeps an IP/host key mapping around. The first time you connect, it doesn't have that, and wants you to know that it's trusting the remote host to be who it claims to be. > Then I disconnect from B and connect again: 'ssh B'. It works without > the "authenticity" warning, but it prompts for the passphrase > again. Blech. ;-p Is there a way to set this up so I don't have to > type the passphrase in all the time? Having to type the passphrase > makes doing 'ssh B <command>' from a script kind of troublesome. I haven't fooled with passphrases. You may need to set things up without one. However, according to the ssh-keygen man page, you need to copy the .ssh/identity.pub key into .ssh/authorized_keys on the remote machine. I'd try that first. <mike -- Mike Meyer http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant, email for rates. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14883.4408.235484.60031>