** Changed in: gnome-keyring
Status: Incomplete = Fix Released
** Changed in: gnome-keyring
Importance: Unknown = Medium
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you
Every time I install a later version of Ubuntu, and mount my previous
versions /home partition during installation, I get prompted for keyring
authentication for any encrypted wireless networks I attempt to connect
to.
Here's how I have to solve this problem each time:
Also noticed that the 'ssh-add' fix worked for me. Should have tried it
before my previous post!
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which
I also have this issue, but only since I rebuilt the ssh server (Ubuntu Server
10.04 LTS) and created new keys. My client (Lucid) hasn't changed other than
routine updates and I don't recall any ssh ones there.
The SSH_AUTH_SOCK fix works.
--
gnome-keyring-daemon returns Agent admitted
I have the same issue on a new install of Lucid i386 on a Lenovo T61.
The ssh-add fix does not work, but unsetting SSH_AUTH_SOCK does.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because
Well I've run into the same problem no longer than yesterday and as a
matter of fact some minutes ago
ssh g...@github.com .. fails with:
...
debug1: Server accepts key: pkalg ssh-rsa blen 277
Agent admitted failure to sign using the key.
...
SSH_AUTH_SOCK=0 ssh -v g...@github.com .. succeeds
Seems to be fixed now in Lucid, both 32-bit and 64-bit.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I started with a stock Karmic Gnome desktop running (other than a bunch
of packages like openssh-server, openssl, etc installed). Ran ssh-
keygen -b 4096 and put a passphrase on the key. now:
- $ git clone git://etc -- fails with github Agent admitted failure to sign
using the key.
- $
I upgraded to Karmic 9.10. Subversion v1.6 now fails, with:
svn up --username myname
Password for 'login' GNOME keyring:
svn: OPTIONS of 'http://svn-repository': authorization failed: Could not
authenticate to server: rejected Basic challenge (http://svn-repository)
Note that I am using
I attempted to upgrade (back when it was alpha 2), but the process
bombed out so I installed Karmic over the top of a copy of a happy
Jaunty install. The system is stable, upgrading OK, and I'm keeping it
up to the minute with updates.
Currently, running 2.6.31-10-generic #32-Ubuntu SMP Thu Sep
I have 5 computers running Karmic (2-x86 and 3-x86_64). I can't reproduce this
issue. To me it seems to be gone.
Did you upgrade to Karmic or do a fresh install, CPKS?
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You
closing since that works now
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed = Fix Released
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Using Karmic with latest updates, 2.6.31-9-generic #29-Ubuntu SMP Sun
Aug 30 17:39:26 UTC 2009 x86_64, I still get the Agent admitted
message, but am then asked for the appropriate passphrase and then ssh
connects appropriately. Unsetting SSH_AUTH_SOCK suppresses the Agent
admitted message.
--
Using Karmic with latest updates, 2.6.31-9-generic #29-Ubuntu SMP Sun
Aug 30 17:39:26 UTC 2009 x86_64, I still get the Agent admitted
message, but am then asked for the appropriate passphrase and then ssh
connects appropriately. Unsetting SSH_AUTH_SOCK suppresses the Agent
admitted message.
--
could you try if that's still an issue in the current karmic version?§
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sebastien, that is as current as Karmic gets. No problems. Bug is
gone.
Sorry if I miss understood your question.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of
Thanks for the update that was the question indeed, it would be nice if
other people on this bug could confirm that the issue is fixed for them
too
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug
With a latest patched karmic, if I copy a dsa key in as .ssh/identity,
then try to ssh to another host, then I get a gui request box asking for
they passphrase, and I then get connected to the host. So it seems like
it works for me.
--
gnome-keyring-daemon returns Agent admitted failure to sign
I just did a fresh install of Karmic alpha 4 and did all updates. The
bug is completely gone.
I don't know if it was fixed from this bug report, but BIG THANKS to
those that fixed it.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
Confirm still apparent in Kamic alpha 3, 2.6.31-6-generic #25-Ubuntu SMP
Fri Aug 14 16:25:04 UTC 2009 i686
geo...@georgenotebook:~$ ssh mythtvbox date
Agent admitted failure to sign using the key.
geo...@mythtvbox's password:
WITH SSH_AUTH_SOCK=0 WORKAROUND:
geo...@georgenotebook:~$
Still apparent in Karmic alpha 3, 2.6.31-5-generic #24-Ubuntu SMP Sat
Aug 1 12:47:58 UTC 2009 x86_64
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs,
The bug was confirmed by at least 3 users.
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of
I think something like this is more important than low.
This was really driving me crazy for a day, I don't restart too often my
PC (each two days), so thankfully I got here searching for Agent
admitted failure to sign using the key.
Problem for me is I can't restart till tomorrow, and I can't
https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/328127/comments/29
Sorry to double post, but I tried this (using passphrase) and everything
went as expected (not need to reboot). So I think that what he said: It
seams that seahorse does not like the key pair being modified
I can confirm that the steps provided by Pedro do work on Jaunty AMD64
when the new key-pair must be created and setup in Seahorse.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you
Setting status to new, since I believe anyone is able reproduce this issue
based on my last message.
Waiting for confirmation.
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete = New
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
I'm using jaunty i386 and I started to experience the same issue.
Everything was ok then I generated a keypair using ssh-keygen with a
non-empty passphrase. I copied it to my target machine's
.ssh/authorized_keys file and ssh command was able to log in (the
passphrase was asked in a window
The steps Pedro Pedruzzi describes
(https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/328127/comments/29) are identical to the steps that
originally produced the bug for me. (However, I did not go as far as he
did to reproduce it again after rebooting.)
--
gnome-keyring-daemon
I am experiencing the same issue by generating the private rsa key from
seahorse and from inside the cli as well.
Seahorse and ssh-copy-id both copy the key to the remote user, but every
time I try to connect, the error message gets shown.
No errors get logged inside my home/.xsession-errors,
** Description changed:
Binary package hint: gnome-keyring
Since upgrading to Jaunty, gnome-keyring-daemon doesn't let me
authenticate to other hosts using my ssh rsa key anymore.
mdesl...@mdlinux:~$ ssh mdesl...@192.168.66.1
Agent admitted failure to sign using the key.
Just submitted my previous post (with private/public keys) to
http://bugzilla.gnome.org/show_bug.cgi?id=571422
BTW: isn't it bad/confusing to double post? Which site should be the
preferred one?
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
Oh, I should have checked this before posting my last comment.
myu...@myserver:~$ echo $SSH_AUTH_SOCK
myu...@myserver:~$
Maybe that's why I'm not having a problem any more?
(for context, see
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/328127/comments/23
where I mention that
After I rebooted, I have never seen the problem again. I'm not sure why
it was transient in my case. And I didn't do anything (afaik) to resolve
it, but it is gone.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received
I'd say once the bug was confirmed upstream it would make sense to
perform further work there.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have the problem on a brand new Jaunty AMD64 install. As Johnathon
wrote, I can reproduce the error and also can use the setting of
SSH_AUTH_SOCK=0 to temporarily bypass it.
To reproduce, I open a terminal and type ssh myu...@myserver.
I do this command many times per day to different servers
somebody having the issue needs to reply to upstream comments
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed = Incomplete
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification
I too am having this issue having upgraded from Intrepid.
The SSH_AUTH_SOCK trick seems to work, as does generating a new key (Something
I am loathed to do I have a number of current keys which are used in a number
of places and I don't fancy regenerating them all) I am using the following
If this was fixed at one time, it has now regressed because I am using
all latest Jaunty packages, and I can reproduce the error and also can
use the setting of SSH_AUTH_SOCK=0 to temporarily bypass it...
** Changed in: gnome-keyring (Ubuntu)
Status: Fix Released = Confirmed
--
I upgraded to Jaunty last night, and now I have this problem
(2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64
GNU/Linux).
Unlike the previous commenter, I was getting no request for my password
to unlock the keyring.
Having read through the comments on bug #328445, I found
** Changed in: gnome-keyring
Status: Unknown = Incomplete
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Works fine here, anyone still affected should file a new bug.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
the bug described there has been fixed please open a new one if you have
a similar issue
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete = Fix Released
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You
I forwarded your comment to the developers. Please don't use the status
In Progress unless you are working on fixing the issue. You can learn
more about bugs status at https://wiki.ubuntu.com/Bugs/Status. Thanks
for your help.
** Changed in: gnome-keyring (Ubuntu)
Status: In Progress =
Comment from Upstream:
I'm really interested in more specific failures, or an SSH key that'll help me
solve the problem:
* If gnome-keyring-daemon is crashing, I need a backtrace.
* If there's lines in /var/log/auth.log or ~/.xsession-errors I need those.
* Or I need a key that I can use to
Does not work for me.
Please re-open.
an...@saltatrix:~$ dpkg -l | grep gnome-keyring
ii gnome-keyring 2.25.91-0ubuntu1
GNOME keyring services (daemon and tools)
ii libgnome-keyring0 2.25.91-0ubuntu1
Seems gnome-keyring 2.25.91-0ubuntu1 fixes this. Can anyone confirm?
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Works for me too now with 2.25.91-0ubuntu1. If anyone still sees this
problem after installing this update, feel free to reopen the bug.
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged = Fix Released
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
works here as well.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
works for me too. Closing bug.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same issue on Jaunty amd64. gnome-keyring 2.25.90-0ubuntu2:
orma...@ormandj-laptop:~$ ssh neutron -v
OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to neutron [192.168.1.100] port
What is even more weird is that if you generate a new private/public key
with ssh-keygen it'll work (after it's copied to the host again) until
next reboot.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug
I'm also seeing this issue on Jaunty amd64, it is keeping me from being
able to do svn update from svn.gnome.org, lol.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member
** Tags added: regression-potential
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm on Xubuntu Intrepid amd64 with gnome-keyring: Installed:
2.24.1-0ubuntu1 and I've got similar problems.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
bug open on http://bugzilla.gnome.org/show_bug.cgi?id=571422 now
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed = Triaged
** Bug watch added: GNOME Bug Tracker #571422
http://bugzilla.gnome.org/show_bug.cgi?id=571422
** Also affects: gnome-keyring via
See also Bug #328445, which looks like a dupe.
:-Dustin
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Confirmed on Jaunty amd64 after upgrading to 2.25.90, post-install.
There seem to be an awful lot of reports, going back to Hardy. This has
bitten or is going to bite quite a lot of people, since seahorse is
effectively a required core component of Ubuntu (ex. Server?).
--
gnome-keyring-daemon
Downgrading to 2.25.4.1-0ubuntu1 solves this for me.
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
thank you for your bug report, the agent is working fine for me, could
you open the bug on bugzilla.gnome.org since you get the issue?
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
gnome-keyring-daemon
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
60 matches
Mail list logo
