After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 584037 - Spits warnings for SSH v1 keys
Spits warnings for SSH v1 keys
Status: RESOLVED FIXED
Product: gnome-keyring
Classification: Core
Component: general
2.26.x
Other Linux
: Normal minor
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-05-27 19:10 UTC by Josselin Mouette
Modified: 2010-02-07 18:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Josselin Mouette 2009-05-27 19:10:37 UTC 
Original report by Johan Walles: http://bugs.debian.org/530770

When there is a identity.pub file with a SSH v1 key in .ssh, gnome-keyring spits a pair of warnings:

May 26 21:16:32 localhost gnome-keyring-daemon[3202]: Unsupported or unknown SSH key algorithm: 1024
May 26 21:16:32 localhost gnome-keyring-daemon[3202]: couldn't parse data: /home/johan/.ssh/identity.pub: Kunde inte tolka publik SSH-nyckel

It should probably entirely ignore such keys instead, or warn that they are not supported anymore.
Comment 1 Stef Walter 2009-07-18 20:18:21 UTC 
Could you attach such a key? Thanks!
Comment 2 Tobias Mueller 2010-02-04 15:45:35 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Josselin Mouette 2010-02-04 17:16:07 UTC 
Sorry for not replying earlier.

I don’t have a private SSH v1 key handy, but the original reporter attached a public key (which is the one gnome-keyring stomped upon):

1024 35 142170279913792228225077639427240465636092050813670295418339452046725255235023543013285496088539381921530791786767488124006833238576190313421439056527490554234994407848975028965073106321535793037036885079113413485324453787849311678185355964433236501964866590054845036063852098525813869441189705812355517075821 johan@foo
Comment 4 Stef Walter 2010-02-07 18:06:14 UTC 
Thanks. Now fixed:

commit 18b360620e069d5e635378b89c1de519982f5e4c
Author: Stef Walter <stef@memberwebs.com>
Date:   Sun Feb 7 18:05:18 2010 +0000

    [ssh-store] Don't warn on SSHv1 keys.
    
    Fixes bug #584037. Don't print out any warning when
    encountering SSH v1 keys in ~/.ssh