From owner-freebsd-questions Mon Nov 27 18:22:35 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 6563A37B479 for ; Mon, 27 Nov 2000 18:22:33 -0800 (PST) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 8341A3E08; Mon, 27 Nov 2000 18:22:32 -0800 (PST) Subject: Re: Help Understanding SSH To: mwm@mired.org (Mike Meyer) Date: Mon, 27 Nov 2000 18:22:32 -0800 (PST) Cc: tayers@bridge.com, questions@freebsd.org In-Reply-To: <14883.4408.235484.60031@guru.mired.org> from "Mike Meyer" at Nov 27, 2000 07:58:16 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001128022232.8341A3E08@bazooka.unixfreak.org> From: dima@unixfreak.org (Dima Dorfman) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > tayers@bridge.com types: > > 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 ' 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. This is to get the RSA key working in the first place (identity.pub -> authorized_keys is telling the server that they key can be used to connect to that user's account). What you're looking for is ssh-agent(1) and ssh-add(1). Hope this helps -- Dima Dorfman Finger dima@unixfreak.org for PGP public key. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message