[Desktop-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Summary of problem (for me): * ssh host fails with ssh Agent admitted failure * SSH_AUTH_SOCK= ssh host works just fine * Conclusion: gnome-keyring can't deal with complex keys WORKAROUND: mv $SSH_AUTH_SOCK $SSH_AUTH_SOCK.broken ssh-agent -a $SSH_AUTH_SOCK This is a new instance of

[Desktop-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

Peter: Yes, that's all true (it's a workaround after all), though you could add the ssh-agent command to your startup scripts. I've updated my Stack Exchange answer to reflect that. BTW, you don't actually need the `mv` line since the .broken

[Desktop-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

While this is not a big endian problem, it is a problem and it is NOT solved yet. I doubt it will be solved until Ubuntu bug 1420522 is solved. This is GNOME bug 754028 (Among

[Desktop-packages] [Bug 1420522] Re: It's not possible to create ED25519 SSH keys

There is information on using (but not creating) ed25519 keys in seahorse at bug 201786 and a workaround posted at https://unix.stackexchange.com/a/189646/87770 Here is the seahorse bug: https://bugzilla.gnome.org/show_bug.cgi?id=754028 Related GNOME bugs: