[hardy] seahorse no longer manages ssh keys

Fixed in the coming 2.21.4

I can confirm that v2.21.4 can manage SSH keys again.

Thanks for the fix!

--
BUGabundo :o)
(``-_-´´) http://Ubuntu.BUGabundo.net
Linux user #443786 GPG key 1024D/A1784EBB
My new micro-blog @ http://BUGabundo.net

I was about to file a bug about the seahorse agent managing the SSH passphrase cache.

I used to have seahorse prompting for the SSH passphrase. For instance I typed "ssh myserver", and a dialog popped up automatically.

Now I have to type "ssh-add" before I can use my passphrase.

But the seahorse agent is still running:

herve 6400 0.0 0.3 22296 6872 ? Ss 09:33 0:00 /usr/bin/seahorse-agent --execute x-session-manager
herve 10198 0.0 0.3 45496 7676 ? Ss 12:22 0:00 seahorse-agent

And in the seahorse application, my SSH key is listed.

However, in the "Searhose Preferences" dialog, I think I lost a tab for managing the SSH key.

Yet I have the version you mention:

ii seahorse 2.21.4-0ubuntu1 A Gnome front end for GnuPG

Sorry, but this is a different bug.

If you go to Seahorse>Key>Create new key, it listed only PGP keys and not SSH keys, which was a bug and is now fixed.
Yours is a different thing. Create a different bug.

On Wednesday 16 January 2008 11:38:26 Hervé Cauwelier wrote:
> However, in the "Searhose Preferences" dialog, I think I lost a tab for
> managing the SSH key.
>
> Yet I have the version you mention:
>
> ii seahorse 2.21.4-0ubuntu1
> A Gnome front end for GnuPG

$ seahorse --version
** Message: init gpgme version 1.1.5
GNOME seahorse 2.21.4

Mine works great.
I guess its a prob with your install.

--
BUGabundo :o)
(``-_-´´) http://Ubuntu.BUGabundo.net
Linux user #443786 GPG key 1024D/A1784EBB
My new micro-blog @ http://BUGabundo.net
ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by...

Reopening since Seahorse 2.21.91-0ubuntu2 can't manage SSH keys again.

Looks like a missing build-dependency. I'll take care of this.

From http://launchpadlibrarian.net/11823389/buildlog_ubuntu-hardy-i386.seahorse_2.21.91-0ubuntu2_FULLYBUILT.txt.gz

checking for ssh-keygen... failed
checking for ssh... failed

SSH Support:

(it should be "SSH Support: yes")

As slomo pointed out to me on IRC, the 08_force_ssh patch is there to enable ssh support without installing openssh-client in the buildds.

The problem was that 10_relibtoolize wasn't generated properly. This debdiff fixes it.

This bug was fixed in the package seahorse - 2.21.91-0ubuntu3

---------------
seahorse (2.21.91-0ubuntu3) hardy; urgency=low

  [ Alexander Sack ]
  * xulrunner 1.9 support patch
    - add debian/patches/09_xul1.9.patch
    - update debian/patches/series
  * rerun autotools accordingly; this fixes SSH support as well (LP: #174441)
    - update debian/patches/10_relibtoolize.patch
  * explicitly use --with-gecko=libxul-unstable
    - update debian/rules
  * update build depends s/firefox-dev/xulrunner-1.9-dev/
    - update debian/control{.in}

  [ Andrew Starr-Bochicchio (andrewsomething) ]
  * change keyservers (LP: #86796)
    - add debian/patches/11_ubuntu_keyserver.patch
    - update debian/patches/series

 -- Alexander Sack <email address hidden> Mon, 18 Feb 2008 11:27:35 +0100

It looks like only one ssh key can be managed :

ii seahorse 2.21.91-0ubuntu3

I have two set of keys : work and personal

Seahorse detected my keyring for connection to work (id_rsa) but ignored ju_rsa, my personnal keyring. Only the first appears in the tab : Trusted keys.

Julien Rottenberg wrote:
> It looks like only one ssh key can be managed :
>
> ii seahorse 2.21.91-0ubuntu3
>
> I have two set of keys : work and personal
>
> Seahorse detected my keyring for connection to work (id_rsa) but ignored
> ju_rsa, my personnal keyring. Only the first appears in the tab :
> Trusted keys.
>

That's not related to this bug. And seahorse only looks for the default names.
Since you gave it a different one, can't you import it with Key->Import?

On Tuesday 26 February 2008 14:33:42 Julien Rottenberg wrote:
> It looks like only one ssh key can be managed :
>
> ii seahorse 2.21.91-0ubuntu3
>
> I have two set of keys : work and personal
>
> Seahorse detected my keyring for connection to work (id_rsa) but ignored
> ju_rsa, my personnal keyring. Only the first appears in the tab :
> Trusted keys.

I dont even have my key on the Trusted Keys. Mine is only on in the Personal tab.
Only keys from friends are in teh Trusted tab.

I thought this bug had been closed, since it has been fixed for some time.

 status fixreleased

--
BUGabundo :o)
(``-_-´´) http://Ubuntu.BUGabundo.net
Linux user #443786 GPG key 1024D/A1784EBB
My new micro-blog @ http://BUGabundo.net
ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by...

> That's not related to this bug. And seahorse only looks for the default names.

I didn't do anything special in Gutsy (as far as I know) to use my 2 keys.

> Since you gave it a different one, can't you import it with Key->Import?

I tried that, "invalid file format" error.

I can open a new ticket if needed, I put my issue here because the bug was saying "... no longer manages ssh keyS" ;-)

Julien Rottenberg wrote:
>> Since you gave it a different one, can't you import it with
> Key->Import?
>
> I tried that, "invalid file format" error.

Hmm, perhaps that's for GPG keys only.

>
> I can open a new ticket if needed, I put my issue here because the bug
> was saying "... no longer manages ssh keyS" ;-)
>

Please do. This was because seahorse was built without ssh support at all. It's
built now, and you said you have an ssh key ;)

To clarify: when I opened this bug, I should have mention that I have several GPG Keys but only one SSH.
Also this bug was against Hardy and not Gutsy.

I have seahorse 2.22.0 and I can see a lot of ssh keys in "my personal keys" tab.

I like to refer to the original bug title. Although I can see my ssh keys I'm not being asked for passphrases if they are needed.

I'm trying to connect via ssh to a certain host. I can see the key for this host in "my personal keys" tab of seahorse. And seahorse-agent is running. I only get a "permission denied (public key)".

It looks like this package should depend on pinentry, or at least suggest it. If pinentry missed it doesn't ask ssh password.