GNOME Bugzilla – Bug 533414
Fails to provide SSH keys to SSH on PowerPC (or general big endian?)
Last modified: 2011-03-09 16:54:31 UTC
Hi, with seahorse 2.22 it's impossible to use the ssh-agent functionality of seahorse on PowerPC machines (or maybe all big endian). See https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/201786 The same key and server works with the same configuration on x86.
So apparently the SSH agent functionality is in gnome-keyring now ;)
Also it works fine on PPC when disabling the SSH functionality of gnome-keyring OR when starting a new gnome-keyring (current one is started via PAM/GDM) and using the new SSH_AUTH_SOCK.
Ok, it fails in ssh/gkr-ssh-daemon.ops.c at line 444 gcry = gcry_pk_sign (&ssig, sdata, s_key); The return value is GPG_ERR_INV_OBJ, i.e. "Invalid Object". Any ideas? :)
Small data point - I see the same bug on Debian PPC.
This is going to be a tough one for me to fix without a PPC machine or big endian machine. But I'll try my best. Any help is welcome.
Maybe obvious, but there's always QEMU with a PowerPC target - last time I tried it, it worked pretty well, albeit slow of course.
I'm sorry that I didn't get to this for 2.26.x versions. I'd really love to fix it, and test it. I just haven't had a chance to get things all setup. On the other hand much of the SSH agent code was refactored, and this may have fixed itself. But that's a long shot :)
If this is still broken for people, one thing I'd think was worth trying would be to generate some ssh keys on the PPC, confirm they don't work with gnome-keyring on PPC, then try those same keys on another architecture (x86). Then do the reverse: generate a keypair on x86, confirm they work then try them on PPC.
Yes, that's a good idea. Another fix also just went into gnome-2-26 branch which had to do with bit lengths, and may have fixed this problem. See bug #576700
No response, closing.