Bug 1224 - ssh-add man page does not fully describe -d option
Summary: ssh-add man page does not fully describe -d option
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Documentation (show other bugs)
Version: -current
Hardware: All All
: P3 trivial
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks: V_4_7
  Show dependency tree / graph
 
Reported: 2006-09-03 04:36 AEST by Andrew McCarthy
Modified: 2008-04-04 09:55 AEDT (History)
1 user (show)

See Also:

Attachments
Suggested patch for man page (496 bytes, patch)
2006-09-03 04:49 AEST, Andrew McCarthy 		no flags Details | Diff
View All 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 Andrew McCarthy 2006-09-03 04:36:15 AEST 
As far as I understand the source, when using the -d option to ssh-add it looks for the public key rather than the private key to remove an identity. This should be documented. The man page should also explain that it will search for <filename>.pub as well while trying to find it.

Thanks!
Comment 1 Andrew McCarthy 2006-09-03 04:49:38 AEST 
Created attachment 1180 [details]
Suggested patch for man page
Comment 2 Justin Lindberg 2007-01-31 08:40:53 AEDT 
I stumbled upon this bug when I was trying to remove an identity
and I did not have the public key file available.

In fact, I consider it a bug that a key file needs to be
available when removing an identity.  There should be a way
to specify the identity to be removed without accessing a file.
What if I added an identity from a file system (on removable
storage) that is no longer available?

Currently, in this case, I have no choice but to remove all
identities.  There doesn't seem to be any technical reason
for this restriction.
Comment 3 Damien Miller 2007-06-12 17:41:48 AEST 
Similar fix applied, it will be in OpenSSH 4.7 - thanks!
Comment 4 Damien Miller 2008-04-04 09:55:55 AEDT 
Close resolved bugs after release.