Updated Chromebook and now I can't ssh into it (password entry failed)

[Simon Que]

I put a newly built test image on my Peppy Chromebook using cros flash over ssh. Now I can't ssh into it as root. I can still ping it. I can still log in as root/test0000 from the VT2 terminal on the Chromebook itself.

Here's the output:

sque@sq:~ $ ssh ro...@100.102.21.87

Warning: Permanently added '100.102.21.87' (RSA) to the list of known hosts.

Password: 

Permission denied (publickey,keyboard-interactive).

What's the solution here?

Simon

[Simon Que]

Is this a known change and WAI?

I can do chronos + sudo but then I get kicked out of sudo when I restart ui:

localhost log # restart ui

Connection to 100.102.21.87 closed by remote host.

Connection to 100.102.21.87 closed.

On Tue, Jun 7, 2016 at 2:44 PM, Dmitry Torokhov <dt...@google.com> wrote:

SSH as chronos and then sudo?

Thanks,
Dmitry

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Vadim Bendebury]

does key based authentication not work?

--vb

--

[Mike Frysinger]

looks like openssh default config disabled root pw access.  we're in process of fixing.  see b/29163543.

log in as non-root, or use ssh keys in the mean time.

-mike

--

[Richard Barnette]

> On Jun 7, 2016, at 1:07 AM, Simon Que <sq...@chromium.org> wrote:
>
> Is this a known change and WAI?
>
> I can do chronos + sudo but then I get kicked out of sudo when I restart ui:
>

You're kicked out at 'ui' restart because the 'ui' upstart
job kills all 'chronos' user processes when it restarts.
That part is WAI.

Based on the comment from vapier@, it sounds like the inability
to log in as root with a password is a known bug.

If it's really important to stay logged in across the 'ui'
restart, you'll need to log in using the ssh test keys. Mostly,
that just means changing ~/.ssh/config. My config looks like
this:

Host 100.96.50.* 100.96.51.*
User root
CheckHostIP no
IdentityFile %d/.ssh/testing_rsa
Protocol 2

You'll need to copy the testing_rsa files from their home
under src/scripts (I forget the exact location, just poke
around).

[Marc]

On Tuesday, June 7, 2016 at 9:00:32 AM UTC-7, Richard Barnette wrote:

Based on the comment from vapier@, it sounds like the inability
to log in as root with a password is a known bug.

If it's really important to stay logged in across the 'ui'
restart, you'll need to log in using the ssh test keys.  Mostly,
that just means changing ~/.ssh/config.  My config looks like
this:

Host 100.96.50.* 100.96.51.*
    User root
    CheckHostIP no
    IdentityFile %d/.ssh/testing_rsa
    Protocol 2

Or with ssh-agent running: ssh-add ~/.ssh/testing_rsa

A carefully aimed "StrictHostKeyChecking no" is also useful.

Typing to log into test images is a sheer waste of time and can easily be avoided.