You are not logged in.
Hi guys,
After I upgraded to GNOME 3.28 it seems to have caused GNOME Keyring to stop being accessible as an agent to get the password for my RSA keys, which means now I have to keep typing them instead of having them accessible through the keyring. Also, I'm having this error when trying to list the added keys:
$ ssh-add -L
error fetching identities: invalid format
Any ideas what might be happening? Is this perhaps a genuine bug, or did I perhaps forget some step to have my keyring working fine with SSH?
Thanks,
Diogo
Last edited by diogobaeder (2018-05-18 16:39:20)
Diogo Baeder
http://diogobaeder.com.br/
Offline
I have the same issue.
meanwhile I use my own launched ssh-agent:
eval $(ssh-agent)
ssh-add
After that no passphrase is asked again.
Offline
Great, I'll do that too :-)
Diogo Baeder
http://diogobaeder.com.br/
Offline
I use Artix Linux ({Arch Linux} - {systemd}) and I can replicate this same behavior. Funny thing: I tried rollback the upgrade from the previous at archive.archlinux.org but didn't worked... I'm complaining about... why?
This bug is so weird. Anyway, using
eval $(ssh-agent); ssh-add
works only terminal-session wide. I'm using gnome-keyring-{daemon, demon, hell} just to solve this problem: system session-wide credentials auth.
I hope we can do something about that... SSH keys and agents is always a hell to debug.
PS.: unrelated, but just FYI about how big is the hell of gnome-keyring-daemon: https://github.com/magit/ssh-agency/issues/12
EDIT:
gnome-keyring 1:3.27.2-1 works as expected, just rollback at:
sudo pacman -U https://archive.archlinux.org/packages/g/gnome-keyring/gnome-keyring-1%3A3.27.2-1-x86_64.pkg.tar.xz
Last edited by lerax (2018-03-26 22:30:40)
Offline
Indeed, gnome-keyring 1:3.27.2-1 works for me too. I tried a later version of 3.27, but it failed as 3.28, only that version you pointed out works for me. Thanks for the hint! :-)
I'm blacklisting gnome-keyring on my pacman.conf until this is fixed in the package.
Diogo Baeder
http://diogobaeder.com.br/
Offline
@lerax
Welcome to the forums.
Keep in mind that these forums are for Arch Linux only, if later you have problems you should use the support channels of your distribution.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Hi R00KIE,
This thread is about GNOME being run over Arch Linux, so I believe there's no mistake here (I believe it falls correctly under "Applications & Desktop Environments" for Arch Linux). Unless I missed anything - in which case, please let me know.
Cheers,
Diogo
Diogo Baeder
http://diogobaeder.com.br/
Offline
Same here. I opened a bug in flyspray: https://bugs.archlinux.org/task/57998
Offline
I just updated the bug report: the issue has been resolved in the recently released gnome-keyring-3.28.2.
The problem was gnome-keyring 3.28.0.2 refused to unlock any key if you had an invalid (or old, as in my case) key under `$HOME/.ssh` while previous versions just dropped the invalid key.
Last edited by entidi (2018-05-18 08:01:05)
Offline
Indeed, it's working now for me. Thanks!
Diogo Baeder
http://diogobaeder.com.br/
Offline
I still have the same problem with gnome-keyring 3.28.2-1. Only downgrading helps. I've also removed all but one RSA key from my .ssh folder for testing but it just does not work.
When I try to connect to a remote machine I always get
sign_and_send_pubkey: signing failed: agent refused operation
debug2: we did not send a packet, disable method
Trying to run ssh-add keyname
gives me invalid-format.
Offline