You'll still get an ssh-agent, only now it will behave sanely: no keys autoloaded, you run ssh-add to add them, and if you want to delete keys, you can. Go to System -> Preferences -> Startup Applications, and unselect the " SSH Key Agent (Gnome Keyring SSH Agent)" box - you'll need to scroll down to find it. What you really want to do is to turn off gpg-keyring-daemon altogether. Now you should be able to do git push without a problem.If necessary you can also open seahorse and delete the keys from there. Navigate to your ~/.ssh folder and move all your key files except the one you want to identify with into a separate folder called backup.The automatically added keys, but is not much use since gnome-keyring will ask you to unlock them anyways when you try doing a git push. Do ssh-add -D to delete all your manually added keys.This bug is still confirmed in Ubuntu 14.04.4, as recently as two days ago (August 21st, 2014) If there are too many, the server will reject the connection.Īnd since gnome-keyring-daemon has decided for itself how many keys you want your ssh-agent to have, and has autoloaded them, AND WON'T LET YOU DELETE THEM, you're toast. The failure is compounded because newer ssh clients automatically try all the keys in your ssh-agent when connecting to a host. How do we hate this? Let's not count the ways - life's too short. And it won't let you delete those keys.ssh directory, and automatically adds any keys it finds to your agent. It subverts the normal operation of ssh-agent, mostly just so that it can pop up a pretty box into which you can type the passphrase for an encrypted ssh key.GitHubtakes the first one which matches, so you always appear as your 'home' user to GitHub, with no way to upload things to work projects.Īllowing ssh-add -d to apply to automatically-loaded keys (and ssh-add -t X to change the lifetime of automatically-loaded keys), would restore the behavior most users expect. So, for example, if you have two different automatically-loaded ssh identities associated with two different GitHub accounts - say for work and for home - there's no way to switch between them. This is the original bug, and it's still definitely present. There is no way to delete automatically added keys. Ssh-add -d/-D deletes only manually added keys from gnome-keyring. Also, why are all identities auto-added?" " Ubuntu: ssh-add -D deleting all identities does not work." Debian Bug report #472477: ssh-add -D does not remove SSH key from gnome-keyring-daemon memory".Note that there are at least two bug reports for ssh-add -d/-D not removing keys:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |