It looks like this package should depend on pinentry, or at least
suggest it. If pinentry missed it doesn't ask ssh password.
--
[hardy] seahorse no longer manages ssh keys
https://bugs.launchpad.net/bugs/174441
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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 "
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.
--
[hardy] seahorse no longer manages ssh keys
https://bugs.launchpad.net/bugs/174441
You received this bug notification because you are a membe
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 man
> 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 tick
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
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 keyrin
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 :
Tr
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
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.
** Attachment added: "seahorse.debdiff"
http://launchpadlibrarian.ne
** Attachment added: "seahorse.debdiff"
http://launchpadlibrarian.net/12051845/seahorse.debdiff
--
[hardy] seahorse no longer manages ssh keys
https://bugs.launchpad.net/bugs/174441
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
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")
** Cha
Reopening since Seahorse 2.21.91-0ubuntu2 can't manage SSH keys again.
** Changed in: seahorse (Ubuntu Hardy)
Status: Fix Released => Confirmed
--
[hardy] seahorse no longer manages ssh keys
https://bugs.launchpad.net/bugs/174441
You received this bug notification because you are a member
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
$ seahors
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.
** Changed in: seahorse (Ubuntu)
Status: New => Fix Released
--
[hardy] seahorse
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
** Changed in: seahorse (Ubuntu)
Status: Fix Committed => Fix Released
--
[hardy] seahorse no longer manages ssh keys
https://bugs.launchpad.net/bugs/174441
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
Fixed in the coming 2.21.4
** Changed in: seahorse (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Emilio Pozuelo Monfort (pochu)
Status: New => Fix Committed
--
[hardy] seahorse no longer manages ssh keys
https://bugs.launchpad.net/bugs/174441
You received this
18 matches
Mail list logo
