Chrome OS Beta Secure Shell: connection refused

454 views
Skip to first unread message

Ahlrimante Yates

unread,
Sep 2, 2017, 6:11:54 PM9/2/17
to Chromium OS dev
Hi,

I am on the newest version of Chrome OS (Beta), and since R59 my sshd is being turned off....or at the least, refusing my connection. I am accessing localhost (chronos@localhost). This happens every time I update and I'm having to keep powerwashing my computer. Is there any reason this would be occurring?

Thanks.

Mike Frysinger

unread,
Sep 2, 2017, 6:37:13 PM9/2/17
to Ahlrimante Yates, Chromium OS dev
CrOS doesn't start sshd automatically.  can you describe in more detail your setup ?
-mike

--
--
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


Ahlrimante Yates

unread,
Sep 2, 2017, 6:46:01 PM9/2/17
to Chromium OS dev
Yeah.

So, I Powerwash and, with Developer mode enabled, enable ssh-debugging-features at the start of Chrome OS and set the root password. I the proceed to install Chromebrew and a number of packages (node, go, etc.), and use them via Secure Shell which is my preferred terminal as opposed to Ctrl-Alt-t. I end up changing chronos password around the time of installing said packages.

The error I get is Secure Shell declines me for chronos@localhost and Ctrl-Alt-t doesnt allow me to access root and my chronos password has been changed to whatever it is. I'm thinking that occurs or the password file is being mucked up somehow. I also get the locked passwd file error when trying to change it with Ctrl-Alt-ForwardButton as root (which still manages to keep my debugging password) :/

Thanks.

Ahlrimante Yates

unread,
Sep 2, 2017, 11:46:55 PM9/2/17
to Chromium OS dev
So, I haven't figured out the reason why this all occurred, but I ended up removing RootFS to add an upstart script for sshd, and then rebooted. I know it works for now, I'm going to update after the next Chrome OS update to see if anything changes.

Mike Frysinger

unread,
Sep 2, 2017, 11:48:46 PM9/2/17
to Ahlrimante Yates, Chromium OS dev
i suspect the issue is that when the system autoupdates, it throws away the customizations made to the rootfs to enable sshd automatically.  which is largely the init script in /etc/init/.  if you ran `/usr/sbin/sshd`, i think that should start up the ssh server too.
-mike


Thanks.

Ahlrimante Yates

unread,
Sep 2, 2017, 11:54:11 PM9/2/17
to Chromium OS dev, aya...@hnerv.com
Okay. Well, that's rather displeasing :(
Especially since I've been using Secure Shell Chrome App. It makes it a little more of a hassle....which I guess, isn't that big of a deal. Still, I'd like to find a solution to this, however, it might just be re-adding the upstart script every update.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages