In a fresh install of bookworm with GNOME desktop, the problem of
ssh-add -D not removing ed25519 keys still remains in 2023. When
investigating this, I noticed that in the default configuration, there
are at least FIVE separate SSH agent processes running:
1. gnome-keyring-daemon process (the bug
Hi,
So, my workaround for this annoying issue was to use gpg-agent instead.
As a nice side effect, you can then use a gpg key to authenticate.
The tricky part for me was to make sure gnome woudn't try to set
SSH_AUTH_SOCK to gnome keyring anyway.
In case others want to go this route, here i
Hello.
I was just hit by this bug, when I temporarily added some ssh keys to do
some tests to find that it was impossible to remove them from the agent.
I am running an up to date debian sid system as of May 21, 2020.
And I can confirm that still "ssh-add -D" fails to remove keys from the
agent.
There may be other ways to disable the thing but try this:
echo 'Hidden=true' | sudo tee -a
/etc/xdg/autostart/gnome-keyring-ssh.desktop
This still appears to be a problem.
I can't log in to some remote machines because there are too many keys
loaded, and gnome-keyring-daemon won't remove them.
I have been affected by this quite a few times over the years, it has
wasted hours of my time. It means I need to use workarounds whi
I think I just got caught by this.
I'm using Debian Stretch/Mate and I had SSH Gnome keyring launched at
startup (install default, I guess).
Indeed I do see gnome-keyring in ps ax:
1255 ?Sl 0:03 /usr/bin/gnome-keyring-daemon --daemonize
--login
While testing ssh keys, I cre
On Wed, 05 Nov 2014 10:51:48 -0700 Neil Mayhew wrote:
> On Fri, 19 Sep 2014 20:35:41 +0100 Pedro Beja wrote:
> > this is an old bug.
> >
> > Could you please still reproduce this issue with newer gnome-keyring
> version like 3.4.1-5 or 3.12.2-1 ?
>
> Still happening with gnome-keyring 3.14.0-1+b
On Fri, 19 Sep 2014 20:35:41 +0100 Pedro Beja wrote:
> this is an old bug.
>
> Could you please still reproduce this issue with newer gnome-keyring
version like 3.4.1-5 or 3.12.2-1 ?
Still happening with gnome-keyring 3.14.0-1+b1 and openssh-client
1:6.7p1-2 on jessie.
$ echo $SSH_AUTH_SOCK
/run
Hey,
this is an old bug.
Could you please still reproduce this issue with newer gnome-keyring
version like 3.4.1-5 or 3.12.2-1 ?
thanks
regards
althaser
Here is how I managed to work around this problem.
Do ssh-add -D to delete all your manually added keys. This also locks
the automatically added keys, but is not much use since gnome-keyring
will ask you to unlock them anyways when you try doing a git push.
Navigate to your ~/.ssh folder and mov
This bug is present for me too. It's preventing me from using github. Is
there a work around in the mean time?
I'm a developer, where would one go about donating some time to
resolving this issue?
I also think the severity should be raised since this is both a major
security flaw and also a se
On Fri, Jan 27, 2012 at 11:52 AM, Michael Biebl wrote:
> Version: 3.2.2-2
> On 27.01.2012 17:41, C. Scott Ananian wrote:
>> Ping? It's been almost four years now, and this bug is still present.
>> It's causing me troubles with github ssh.
>
> Works fine with gnome-keyring.
Perhaps you don't und
Ping? It's been almost four years now, and this bug is still present.
It's causing me troubles with github ssh.
--scott
--
( http://cscott.net/ )
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Any news on this bug? It is still relevant with gnome-keyring 2.30...
--
Stéphane
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Are you sure "ssh-add -D" above is removing keys from g-k? I wonder
> whether it could be removing keys from ssh-agent but ssh-add -l would
> list them from g-k.
ssh-agent was not running during the test.
ssh-add says the key is removed, but it is still in g-k.
--
To UNSUBSCRIBE, email t
On Mon, Mar 24, 2008, Arnaud Cornet wrote:
> Steps to reproduce:
> # ssh-add -l
> 1024 XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
> # ssh-add -D
> All identities removed.
> # ssh-add -l
> 1024 XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
>
> I am still able to log in with this key afterwar
Package: gnome-keyring
Version: 2.22.0-2
Severity: important
Steps to reproduce:
# ssh-add -l
1024 XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
# ssh-add -D
All identities removed.
# ssh-add -l
1024 XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
I am still able to log in with this key afterwa
17 matches
Mail list logo
