Description of problem: Whenever I'm logging in to a remote host via ssh using my ed25519 key I get prompted for the password. This should not be necessary since I expect the ssh-agent to handle this when I have logged in. Version-Release number of selected component (if applicable): Fedora 25 Gnome 3.22 Seahorse 3.20.0-1 gnupg-1.4.21-1 gnupg-2-2.1.13-2 openssh-7.4p1-4 How reproducible: Always Steps to Reproduce: 1. Generate a ssh key using the keytype ed25519 and enter a password when creating the key: $ ssh-keygen -t ed25519 2. Log out from your computer and log in again 3. Start a ssh session to a remote host: $ ssh user Actual results: I must enter the password every time I log in to the remote host via ssh Expected results: ssh-agent should handle this and I should not be forced to enter my password upon every connection. Additional info: -
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fixed in upstream: https://bugzilla.gnome.org/show_bug.cgi?id=775981 https://bugzilla.gnome.org/show_bug.cgi?id=754028 https://mail.gnome.org/archives/release-team/2018-February/msg00095.html Testing packages available: https://copr.fedorainfracloud.org/coprs/ueno/gnome-keyring/
Confirmed that the copr build above solves the issue.
Still doesn't seem to handle ED25519 keys, though.
Actually, the package has broken runtime dependencies: $ /usr/bin/gnome-keyring-daemon --start --components=ssh /usr/bin/gnome-keyring-daemon: symbol lookup error: /usr/bin/gnome-keyring-daemon: undefined symbol: gcr_ssh_askpass_child_setup $ /usr/bin/gnome-keyring version gnome-keyring: 3.27.90 $ rpm -q gnome-keyring gnome-keyring-3.27.90-0.7.git7b76a41b.fc27.x86_64
(In reply to Dominik 'Rathann' Mierzejewski from comment #4) > Still doesn't seem to handle ED25519 keys, though. I was maybe a bit unclear on what this copr "fixes". What that build provides is a working ssh-agent than enables a SSH key to be connected via ssh-agent to the keyring so you don't need to type the password of the ED25519 key upon every new SSH connection.
(In reply to Dominik 'Rathann' Mierzejewski from comment #5) > Actually, the package has broken runtime dependencies: > > $ /usr/bin/gnome-keyring-daemon --start --components=ssh > /usr/bin/gnome-keyring-daemon: symbol lookup error: > /usr/bin/gnome-keyring-daemon: undefined symbol: gcr_ssh_askpass_child_setup > $ /usr/bin/gnome-keyring version > gnome-keyring: 3.27.90 > $ rpm -q gnome-keyring > gnome-keyring-3.27.90-0.7.git7b76a41b.fc27.x86_64 I can't reproduce the issue you experienced. I get the following output: $ /usr/bin/gnome-keyring-daemon --start --components=ssh SSH_AUTH_SOCK=/run/user/1000/keyring/ssh $ /usr/bin/gnome-keyring version gnome-keyring: 3.27.90 $ rpm -q gnome-keyring gnome-keyring-3.27.90-0.7.git7b76a41b.fc27.x86_64 I have however attempted to create a workaround for this earlier before these copr packages were available, but I can't find the article describing the workaround right now, so it might be that's what differs between our systems.
FWIW, it looks like gnome-keyring does support the ED25519 keys now: $ eval `/usr/bin/gnome-keyring-daemon --start --components=ssh` $ ssh-add -l 256 SHA256:xxxxx/xxxxx/xxxxxxxxxx/xx/xxxxxxxxxxxxx/xxx aaa.ddd (ED25519) However, I still can't import ED25519 private key in seahorse GUI. It says: id_ed25519 Could not display “id_ed25519” Reason: Unrecognised or unsupported data. seahorse-3.20.0-9.fc28.x86_64 gnome-keyring-3.28.2-1.fc28.x86_64
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.