Handling an old ssh key with Seahorse

Hi :slight_smile:

I’m not sure about the difference between Platform and Core categories.

I got a new computer recently. I put Ubuntu on it.

I run ssh-keygen on it, to make a new ssh key, and it’s fine!
Seahorse got it and handles the passphrase perfectly!

Now, I got my old ssh key back from the old computer, and I would like Seahorse to handle it too, so I can access all my remote computers to change the ssh key there.
But I don’t succeed in doing that.

I thought it would be enough to set IdentityFile in ~/.ssh/config, to tell where is the key, but no…

Do you need me to detail everything I tried to do, or is there a tutorial for doing this where I can easily see what I missed?

Is the SSH key stored in a specific location? By default, Seahorse only checks for new keys in ~/.ssh, so if it’ stored somewhere else, that’s probably the reason it can’t find it.

Nope, not in a specific location. In a location which I informed SSH about via IdentityFile.

I’m using seahorse 41.0, which comes with Ubuntu 22 LTS.

Is there a way to store keys elsewehere than in ~/.ssh?

I found how to make it working, but there is 2 conditions:

  • keys must be located directly in ~/.ssh, not even in a sub-directory of it,
  • the public key must be there, with the same name of the private key, whereas SSH does not require it to work.

It’s nice for new users to fully support SSH keys. :slight_smile:
But I manage them via CLI.

I need Seahorse only to store the passphrase in a secure way / restore it in an easy way.
I’m surprised that Seahorse doesn’t handle all cases where SSH asks for the passphrase.

Is it sth which could be improved later? :slight_smile: