Bug 1834 - OpenSSH ignores keys in ~/.ssh/config and offers keys from Seahorse instead
Summary: OpenSSH ignores keys in ~/.ssh/config and offers keys from Seahorse instead
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: 5.6p1
Hardware: All All
: P2 normal
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-08 20:53 AEDT by jchadima
Modified: 2011-01-24 12:33 AEDT (History)
2 users (show)

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 jchadima 2010-11-08 20:53:37 AEDT 
The ssh ignores the "IdentityFile" config in ~/.ssh/config and instead uses the keys from Seahorse in alphabetical order. There is no way how to force the order the keys. This may cause the unability to login on sites with limited numbers of login attempts.
Comment 1 Darren Tucker 2010-11-08 21:39:39 AEDT 
Doesn't "IdentitiesOnly yes" do what you want?
Comment 2 Damien Miller 2010-11-10 10:06:05 AEDT 
from "man ssh_config"

IdentitiesOnly
  Specifies that ssh(1) should only use the authentication identity
  files configured in the ssh_config files, even if ssh-agent(1)
  offers more identities.  The argument to this keyword must be
  ``yes'' or ``no''.  This option is intended for situations where
  ssh-agent offers many different identities.  The default is ``no''.

If you don't want ssh to touch the agent at all, then unset the SSH_AUTH_SOCK environment variable.
Comment 3 Damien Miller 2011-01-24 12:33:39 AEDT 
Move resolved bugs to CLOSED after 5.7 release