Memory leak and completely broken ssh connections on specific keys on 4.2.1-2
Description:
The current version of gcr (4.2.1-2), causes manifolds of issues. For one, there is a weird behavior where certain keys cause the ssh authentication to completely stall. Once stalled, this continues to run in the background, even if the ssh command was terminated. The process in the background will continue to eat up all the available memory during the next hours.
Also reported here: https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/143
Since there is no movement upstream, the suggestion would be to downgrade gcr again, as it is essentially broken in its state right now. Looking at the issue tracker of gcr, this is far from the only issue, but one of the most annoying and nasty one due to the memory leak.
Steps to reproduce:
Update to gcr 4.2.1-2 and coresponding packets:
gnome-keyring: (working 1:42.1-3 => broken 1:46.1-2) libgnome-keyring:(working 3.12.0+13+g4f8ab73-3 => broken 1:3.12.0+r14+g23438cc-1
Use an ssh key with a password to connect to a server with the same ssh key installed. We have specific keys that cause this issue, not really sure what is the properties causing the issue itself.
Current workaround
Manually downgraded all the packages and ignoring them during upgrade:
Warnung: gcr-4: Ignoriere Paket-Aktualisierung (4.2.0-1 => 4.2.1-2)
Warnung: gnome-keyring: Ignoriere Paket-Aktualisierung (1:42.1-3 => 1:46.1-2)
Warnung: libgnome-keyring: Ignoriere Paket-Aktualisierung (3.12.0+13+g4f8ab73-3 => 1:3.12.0+r14+g23438cc-1)