On Fri, 2007-08-17 at 09:13 -0400, Adam Schreiber wrote: > On 8/16/07, Alex Malinovich <demonbane the-love-shack net> wrote: > > I can see my SSH key listed in seahorse, but I have no way of loading > > it. If I try to ssh to a machine, I'm prompted for the password at the > > command line, not by seahorse. I can manually add the key using ssh-add > > but that kind of defeats the purpose. I have verified that > > seahorse-daemon is running and that caching SSH keys is enabled in > > seahorse-preferences. > > Make sure you're properly chaining ssh-agent and seahorse-agent into > your session start up with the directions at > http://live.gnome.org/Seahorse/SessionIntegration. So I spent about a week beating my head against the keyboard trying to figure out what's wrong with no luck. I went over the guide about a dozen times trying everything listed for all of the different distros with still no luck. Finally, I have a solution. It seems that, for whatever reason, seahorse didn't like my key. It's an old DSA 1024-bit key that I've been using for a couple of years now, and seahorse just didn't want to work with it. I generated a new key which defaulted to RSA 2048-bit, and now that key works exactly as it should. I have the passphrase for it stored in the agent, so as soon as I unlock the agent for my session, my keys become available and I can ssh to my heart's content. So is this a known issue? Is there a specific reason that DSA keys wouldn't be handled properly by the agent? I'm content with the new key that I have, but in case this is a bug I would like to offer my help in troubleshooting it if necessary. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837
Attachment:
signature.asc
Description: This is a digitally signed message part