Thierry, that's the option I was looking for and couldn't find, thank
you so much.
Colin, you're right it's seahorse who is adding automatically all keys
it find in ~/.ssh. Happily enough, seahorse respects the IdentitiesOnly
option in ~/.ssh/config, so the mystery is solved :)
** Changed in:
I think it's by design when IdentitiesOnly is not set in .ssh/config or
/etc/ssh/ssh_config. The SSH agent probably proposes other identities ?
Please check out this option and confirm.
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
jaunty openssh-client tries all keys
Oh, yeah, Thierry's very likely spot on here. This is documented in the
ssh_config(5) manual page.
If you don't want to use IdentitiesOnly, you could remove some of those
keys from your agent. Perhaps you're running some agent other than ssh-
agent, such as seahorse, and some bit of the desktop
Yesterday I upgraded my desktop box to jaunty, and now I'm getting this
error when trying to connect to a remote server through ssh with
password authentication:
Received disconnect from {ip address}: 2: Too many authentication failures for
{username}
lost connection
That meaning that I have a
