BTW, ssh-agent $SHELL does what eval `ssh-agent` does...
-chris
-----Original Message-----
From: Darren Tucker [mailto:dtucker@zip.com.au]
Sent: Friday, August 13, 2004 11:46 PM
To: Fouts Christopher (IFNA MP DC)
Cc: secureshell@securityfocus.com
Subject: Re: HELP please! Why is the agent NOT recognized
Christopher.Fouts@infineon.com wrote:
I have 2 machines, remote SSH server is a Linux (RH Fedora) and
local SSH client is HPUX 10.20. I mimiced the steps I did to have
SSH working for user1 for user2. user1 can tunnel through, but not
user2. I gathered the following debug lines for the user2 session,
and it seems like the agent I create is NOT recognized by ssh, at
least I think so as evident from the "No agent" line midway down.
I do...
> ssh-agent $SHELL
> ssh-add
Try:
$ eval `ssh-agent`
$ ssh-add
You need to "eval" the output of ssh-agent to set the environment
variables required to let ssh know how to find the agent.
Recent versions of the ssh-agent man page make this somewhat clearer:
[quote]
There are two main ways to get an agent set up: The first is
that the agent starts a new subcommand into which some
environment variables are exported, eg ssh-agent xterm &. The
second is that the agent prints the needed shell commands
(either sh(1) or csh(1) syntax can be generated) which can be
evalled in the calling shell, eg eval `ssh-agent -s` for
Bourne-type shells such as sh(1) or ksh(1) and eval `ssh-agent -c` for
csh(1) and derivatives.
[/quote]
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the
experience usually comes from bad judgement.
