Ssh keys problem

[Stuart Sears]

On Tuesday 21 March 2006 12:01, Anne Wilson decided we wanted to hear the 
following:
> > ssh-agent is just an empty pocket until you give it your key and
> > passphrase with ssh-add.
>
> That creates id_dsa - which was there before.  Is there some sort of
> clean-up going on, so that it needs to be renewed?
nope.
ssh-keygen -t dsa
would regenerate ~/.ssh/id_dsa{,.pub}
ssh-add just looks for your key (probably id_dsa ) and caches the password you 
type in.
I assume you were seeing something like this...
[stuart at lanky ~]$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-NoFCr14079/agent.14079; export SSH_AUTH_SOCK;
SSH_AGENT_PID=14080; export SSH_AGENT_PID;
echo Agent pid 14080;
[stuart at lanky ~]$ ssh-add
Enter passphrase for /home/stuart/.ssh/id_dsa:

that just wants the password so it can cache it.

incidentally, were you really ssh-ing to localhost (borg) earlier?
<quote>
Warning - the authenticity of host 'borg (127.0.0.1)'... can't be established
</quote>

Regards

Stuart
-- 
Stuart Sears RHCA RHCX
"Quit worrying about your health.  It'll go away."
- Robert Orben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20060321/eb02d5a1/attachment-0001.sig>