[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
I see this bug is still open. One work-around exists where ~/.ssh/config is used. Make an entry there for the host (or range of hosts using a pattern) and assign the right key using IdentityFile while also setting IdentitiesOnly to "yes". Both parts are needed for the work-around. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in GNOME Keyring: Confirmed Status in gnome-keyring package in Ubuntu: Triaged Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
** Changed in: gnome-keyring Status: Unknown = Confirmed ** Changed in: gnome-keyring Importance: Unknown = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in GNOME keyring services: Confirmed Status in gnome-keyring package in Ubuntu: Triaged Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
** Changed in: gnome-keyring (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in GNOME keyring services: Unknown Status in gnome-keyring package in Ubuntu: Triaged Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
** Changed in: gnome-keyring (Ubuntu) Importance: Undecided = High ** Bug watch added: GNOME Bug Tracker #730126 https://bugzilla.gnome.org/show_bug.cgi?id=730126 ** Also affects: gnome-keyring via https://bugzilla.gnome.org/show_bug.cgi?id=730126 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in GNOME keyring services: Unknown Status in gnome-keyring package in Ubuntu: Triaged Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
Seems to be back with 14.04 $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
This bug also messes with tools like FileZilla, preventing it from authenticating with a password. The keyes get tried first, even if they aren't keys for that server, so that it fails before it can even get around to trying the password. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in “gnome-keyring” package in Ubuntu: New Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
While it appears not to be a problem in Lubuntu, it is still a problem in Ubuntu 13.10. $ lsb_release -r Release:13.10 There are really two problems. One is that the keyring or something snarfs up the keys without asking and then offers all of them when trying to connect. The other is that there is no negotiation between the ssh client and server about which key to offer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in “gnome-keyring” package in Ubuntu: New Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
This seems to be partially fixed in Saucy now. Identities are not getting automatically added to the agent. However, if six keys are added to the agent manually, it then still is impossible to authenticate using a seventh key either added to the agent or pointed to manually. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in “gnome-keyring” package in Ubuntu: New Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1195911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
