From owner-freebsd-current Tue Mar 7 18:14:19 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 00F0537BB31; Tue, 7 Mar 2000 18:14:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B606B2E815B; Tue, 7 Mar 2000 18:14:17 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 18:14:17 -0800 (PST) From: Kris Kennaway To: Richard J Kuhns Cc: freebsd-current@FreeBSD.ORG Subject: Re: YA ssh question (ssh-askpass?) In-Reply-To: <14533.29753.499155.780744@localhost.grauel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Richard J Kuhns wrote: > So does all this mean that I now have to start using ssh-add/ssh-agent? Not at all; it's there as an option for people who have "secure" workstations and/or want single-signon for SSH. I often use ssh-agent if I have lots of remote CVS commits to do consecutively, e.g. do 'ssh-agent tcsh' and then ssh-add in the subshell, and exit when I'm done. ssh-add will also only invoke ssh-askpass if invoked with no controlling terminal, e.g. ssh-add < /dev/null or if called during the X login process. Otherwise it uses the good old (internal) text prompt. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message