FS#57998 - [gnome-keyring] 3.28 does not unlock SSH keys

Attached to Project: Arch Linux
Opened by Nicola Fontana (ntd) - Wednesday, 28 March 2018, 06:29 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 18 May 2018, 10:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

From this forum thread: https://bbs.archlinux.org/viewtopic.php?id=235670

Additional info:

$ ssh-add -L
error fetching identities: invalid format

Downgrading to 3.27.2-1 resolves the issue.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Friday, 18 May 2018, 10:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  gnome-keyring 1:3.28.2-1
Comment by Jan de Groot (JGC) - Thursday, 05 April 2018, 22:09 GMT
What's the status with 3.28.0.2-1?
Comment by Nicola Fontana (ntd) - Friday, 06 April 2018, 05:15 GMT
The problem has been introduced by 3.28.0.2-1: locally I don't have any other 3.28 release to test.
The issue can be solved also by downgrading to 3.27.4+8+gff229abc-1 (the more recent working release I have in the pacman cache).
Comment by Nicola Fontana (ntd) - Friday, 18 May 2018, 07:56 GMT
Bug has been reported upstream [1] and the solution [2] has been released in 3.28.2.

The problem is gnome-keyring 3.28.0.2 refused to unlock any key if you had an old SSH1 key under `$HOME/.ssh`.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=795699
[2] https://git.gnome.org/browse/gnome-keyring/commit/?id=f3f3cc7

Loading...