Bug 480 - extend the -l or -L option to mention the ssh-agent's pid
Summary: extend the -l or -L option to mention the ssh-agent's pid
Status: CLOSED WONTFIX
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh-add (show other bugs)
Version: -current
Hardware: All All
: P5 enhancement
Assignee: OpenSSH Bugzilla mailing list
URL: http://www.openbsd.org/cgi-bin/man.cg...
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-30 21:15 AEDT by Ralf Hauser
Modified: 2006-10-07 11:35 AEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Hauser 2003-01-30 21:15:49 AEDT 
I have multiple ssh-agent's running, but I don't know which one is accessed by
my ssh-add command. If with -*extra*l, I could find out, this would be helpful!
Comment 1 Markus Friedl 2003-02-02 00:11:06 AEDT 
this does not belong to the -L or -l option
Comment 2 Ralf Hauser 2003-02-03 04:12:50 AEDT 
So what is your suggestion - add a new option?
Comment 3 Ralf Hauser 2003-02-19 03:02:40 AEDT 
Or another option would be to have ssh-agent complain if it detects other
instances of itself already running under the same userID?
Comment 4 Markus Friedl 2003-02-19 03:18:38 AEDT 
perhaps have ssh-add -v print out the socket name.
Comment 5 Ralf Hauser 2003-02-19 03:48:22 AEDT 
sure, would be great if this additional option could be added...
Comment 6 Damien Miller 2003-02-24 13:25:58 AEDT 
I don't think that making "ssh-add -v" print the socket name would help much -
you can do that yourself with "echo $SSH_AUTH_SOCK"
Comment 7 Darren Tucker 2005-02-09 20:39:25 AEDT 
I don't think there's much to be done for this; as djm points out, figuring out
which agent ssh-add will access is simply a matter of echoing $SSH_AUTH_SOCK (or
$SSH_AGENT_PID for that matter).
Comment 8 Darren Tucker 2006-10-07 11:35:42 AEST 
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.