New issue
Advanced search Search tips

Issue 630106 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

New OpenSSH displays "key_load_public: invalid format" error with ChromeOS test key

Reported by dhend...@chromium.org, Jul 21 2016

Issue description

I recently started having an issue with SSH where whenever I try to log into a DUT from within my CrOS SDK:
$ ssh root@elm
key_load_public: invalid format
Enter passphrase for key '/home/dhendrix/.ssh/identity':

"ssh -V" in my SDK returns "OpenSSH_7.2p2, OpenSSL 1.0.2h  3 May 2016"

If I try to log in from Goobuntu (OpenSSH_7.1p2, OpenSSL 1.0.1f 6 Jan 2014), it works fine.

I have a DUT that is running an older version of SSH, and a DUT that is running 7.1p2. In both cases, SSH'ing from Goobuntu works fine and SSH'ing from the SDK doesn't.

For what it's worth, this just started happening with no intentional changes to my host environment. I've used ssh-agent to manage keys and have done non-interactive login for a very long time, this just recently started happening after I rebooted my workstation and re-entered my CrOS SDK.
 
Summary: New OpenSSH displays "key_load_public: invalid format" error with ChromeOS test key (was: New OpenSSH breaks non-interactive login)
Quick update  - There was something slightly wrong on my side. For some reason I didn't have the ChromeOS test key added in ssh-agent (my bad). After using ssh-add I can now log in non-interactively.

However, I still see "key_load_public: invalid format" when logging in from within the SDK. My ~/.ssh/testing_rsa and ~/.ssh/testing_rsa.pub files are directly copied from chromiumos/src/scripts/mod_for_test_scripts/ssh_keys/testing_rsa, with permissions set to 0600.

So maybe the new version of OpenSSH has a bug where it thinks the key is not formatted correctly?
7.3p1 is out, so we could just upgrade to that
Components: Internals

Sign in to add a comment