ssh signin problem since OTA-10

[Joolz]

Not sure if this is a terminal or image issue, but here goes.

Since the update last night to OTA-10 I cannot ssh to a server anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

On server side and client side nothing changed to the user settings or keys.

[Stefano Verzegnassi (verzegnassi-stefano)]

Hi,

The terminal app hasn't been updated recently, so it's reasonable to think that there's something different in OTA-10.

Having a look at the commit log[1] for the latest release, I see that "gnome-keyring" package has been added to the system image.
A quick search[2] on Google suggests that this may cause the problem you mention.

The blog post at [2] suggests to workaround the problem by running:

$ SSH_AUTH_SOCK=0 ssh <username>@<hostname>

Therefore I'm adding "canonical-devices-system-image" project as affected, and marking the report as Incomplete for terminal-app (so I get notified of any change/update of the report).

=====

[1] http://people.canonical.com/~lzemczak/landing-team/ota/ota-10.commitlog
[2] https://chrisjean.com/ubuntu-ssh-fix-for-agent-admitted-failure-to-sign-using-the-key/

[Joolz (joolz)]

Hi Stefano,

The workaround / setting works. I put it in .bashrc (export SSH_AUTH_SOCK=0) so I don't need to think about it anymore.

Thank you for your quick reaction!

[Phil White (madhemail-launchpad)]

I use my ssh connection to my home server a lot, this was definintely OK before the OTA10 update and the problem occured after it.

Running the ssh command with the -v to give some output gives:-
 I've run it with debug output and I get this output (the ssh-add would account for why it's trying twice).

OpenSSH_6.7p1 Ubuntu-5ubuntu1.4, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to <My IP> [<My IP>] port <My Port>.
debug1: Connection established.
debug1: identity file /home/phablet/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/phablet/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/phablet/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/phablet/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/phablet/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/phablet/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/phablet/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/phablet/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Ubuntu-5ubuntu1.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.8
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.8 pat OpenSSH_5* compat 0x0c000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr <email address hidden> none
debug1: kex: client->server aes128-ctr <email address hidden> none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: RSA <My host key>
debug1: Host '[<My IP>]:<My port>' is known and matches the RSA host key.
debug1: Found key in /home/phablet/.ssh/known_hosts:3
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/phablet/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
Agent admitted failure to sign using the key.
debug1: Offering RSA public key: phablet@ubuntu-phablet
debug1: Server accepts key: pkalg ssh-rsa blen 279
Agent admitted failure to sign using the key.
debug1: Trying private key: /home/phablet/.ssh/id_dsa
debug1: Trying private key: /home/phablet/.ssh/id_ecdsa
debug1: Trying private key: /home/phablet/.ssh/id_ed25519
debug1: No more authentication methods to try.
Permission denied (publickey).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rüdiger Kupper (ruediger.kupper)]

Confirming this problem exists since OTA-10 on Meizu MX4.
Confirming the workaround in comment #1 works.
Related report: bug #201786

[Colin Watson (cjwatson)]

It may well be that we're shipping an SSH agent that isn't handling some key formats correctly, but (unless I see further evidence to the contrary) that doesn't make this a bug in openssh. I'm closing that task, but leaving others open such as the gnome-keyring task.

[Rüdiger Kupper (ruediger.kupper)]

Thanks, Colin! I listed openssh, because it is listed as affected in bug #201786, having status "Confirmed". It may be wrong there, too, or the maintainers had a reason to confirm it. If it helps, have a look at bug #201786.
Regards, Rüdiger

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.