registry team mailing list archive

Thread
Date

[Bug 505278] Re: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?

To: registry@xxxxxxxxxxxxxxxxxxx
From: Rafal-maj-it <505278@xxxxxxxxxxxxxxxxxx>
Date: Mon, 20 Sep 2010 18:43:08 -0000
Reply-to: Bug 505278 <505278@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug looks like medium priority since it can totally block some ssh connections in following way:
user with many keys connects to some server(s) and all his keys are cached.

When he tries to ssh to another server, or filezilla sftp into it, or
sshfs, or many other pubkey usecases,  then often first all the keys
will be tried, often resulting in server disconnecting (instead of
tyring the correct key or instead of using the given plain password).

In example Firezilla appears to first try all pubkeys of the user that started firezilla and that are in the agent (as seen on debug on server-side) instead of first using the given plain password.
Then ssh-agent -D does not help to resolve the problem.

-- 
ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?
https://bugs.launchpad.net/bugs/505278
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for GNOME Keyring.