Bug 1248916 - Unsupported or unknown SSH key algorithm: ssh-ed25519
Summary: Unsupported or unknown SSH key algorithm: ssh-ed25519
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-31 07:15 UTC by Harald Hoyer
Modified: 2018-11-30 22:13 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 22:13:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Harald Hoyer 2015-07-31 07:15:07 UTC
$ rpm -qf /usr/bin/gnome-keyring-daemon
gnome-keyring-3.16.0-2.fc23.x86_64

Comment 1 Jan Kurik 2016-02-24 13:30:03 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 2 Dominik 'Rathann' Mierzejewski 2016-12-02 21:53:45 UTC
Still reproducible on Fedora 25 (gnome-keyring-3.20.0-1.fc25.x86_64).

Comment 3 Dominik 'Rathann' Mierzejewski 2016-12-02 22:06:01 UTC
ECDSA keys are unsupported, too:
unsupported algorithm from SSH: ecdsa-sha2-nistp521

Comment 4 James Boyle 2017-02-01 18:43:19 UTC
related gnome bugs for those interested in tracking:

https://bugzilla.gnome.org/show_bug.cgi?id=754028
https://bugzilla.gnome.org/show_bug.cgi?id=723274

Comment 5 fredrik@mikker.se 2017-03-28 09:09:58 UTC
See related bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1435924

Comment 6 David Gibson 2017-07-13 09:57:35 UTC
Still present in Fedora 26.

This is a pretty serious deficiency.

Comment 7 David Gibson 2017-07-13 10:00:26 UTC
This is made even worse by the fact that the error from ssh-add doesn't say anything about the hey type, so it's not at all obvious what's going wrong.

Comment 8 James Boyle 2018-02-08 20:37:31 UTC
This is still present in Fedora 27, but I am unable to change the bug's version field to 27.  Can someone bump up the version so this doesn't fall through the cracks?

Comment 9 David Gibson 2018-07-20 03:56:07 UTC
Fwiw this seems to be fixed in Fedora 28.

Comment 10 Ben Cotton 2018-11-27 14:57:04 UTC
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.

Comment 11 Ben Cotton 2018-11-30 22:13:47 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.