GNOME Bugzilla – Bug 577842
ssh are using ssh-userauth but ignores private key
Last modified: 2009-04-29 07:10:52 UTC
Please describe the problem: I'm using ssh-add to load a private key but it's used and ignored by ssh, see verbose output "ssh.txt". I think this is the most interesting part: debug1: Offering public key: /some/path/private-key2.txt debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-rsa blen 276 debug2: input_userauth_pk_ok: fp <snipp> debug3: sign_and_send_pubkey It works if I'm using ssh -i /some/path/private-key2.txt but not from agent. It also worked with the agent before I upgraded to 9.04 It seems like Ubuntu and Gnome are using gnome-keyring as ssh agent Original bug report at Launchpad: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/348126 rancor@xps-laptop:~$ lsb_release -rd Description: Ubuntu jaunty (development branch) Release: 9.04 Steps to reproduce: I upgraded three systems from Ubuntu 8.10 to 9.04 and two of them got this issue Actual results: Expected results: Does this happen every time? Yes Other information: ssh-agent works if I start it manualy from a new tty: "ssh-agent bash", then "ssh-add <private key>"
Created attachment 132000 [details] SSH debug
Based on the upstream report, I think this is a duplicate of #576700.
Ok I've reached the limits of my investigative skills for now. I could try a 2.25 version and try to pin down when the bug was introduced, but switching gnome-keyring versions is not too easy for me. To achieve it this time, I built 2.26.1 and installed to /usr/local, and tried changing my session settings to invoke that instead of the one in /usr/bin. My session settings were simply ignored, so I ended up moving the /usr/bin copies aside and symlinking their old paths to the new binaries in /usr/local/bin. If someone could give me a brief pointer on a neater way of switching keyring versions (perhaps within an X session ideally) that would be great. If there's any configure or make flag (or set of fprintfs I could hack in) that might shed light on what is going on pointers in that direction would be great too.
Bugger I keep mailing the wrong bug. Sorry for the noise.
I can confirm the reported bug, attaching a freshly generated RSA 1023-bit key (without a passphrase), which can be used to reproduce. When I generate an RSA 2048-bit key, there are no problems using ssh-agent.
Created attachment 133433 [details] RSA 1023-bit key for which ssh-agent does not work
To reproduce: *** This bug has been marked as a duplicate of 576700 ***