ChromeOS – removing SSH known_hosts from Chromebook

One of the things that is not implemented in the Secure Shell Chrome extension is the ability to remove know_host fingerprints which alert you if the fingerprint for a specific IP address has changed. However there are times when you upgrade a systems and this need to be done. @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is d6:be:12:7e:22:23:c3:e1:56:30:d6:cd:65:b7:ab:42. Please contact your system administrator. Add correct host key in /.ssh/known_hosts to get rid of this message. Offending ECDSA key in /.ssh/known_hosts:7 ECDSA host key for xxxxxxxxxxxxx.yyy.au has changed and you have requested strict checking. Host key verification failed. NaCl plugin exited with status code 255. (R)econnect, (C)hoose another connection, or E(x)it? Here is how to remove a known host fingerprint (from known_hosts) on a Chromebook. You can find the index of the offending host entry reported by ssh if the connection fails (see above: "Offending ECDSA key in /.ssh/known_hosts:7"). Then you can open the JavaScript console (CTRL +Shift +J) and type the following into the console. term_.command.removeKnownHostByIndex(INDEX); Replace INDEX with the number obviously. To clear all the known hosts: term_.command.removeAllKnownHosts();

Continue Reading

Chromebook tips to get started

Just got myself (actually it's for our Office Manager back in OZ) one of these Chromebooks while in Europe (since Google Australia with their absolutely hopeless hardware strategy do not seem to be able to ship any devices - Nexus 4 anyone ?) . Since the first days turned out to be a bit of a frustrating experience, I thought I share some of the findings as I had a hard time finding much useful info on troubleshooting ChromeOS. Wireless Connection (WIFI) Do not use WPA (or for that matter WEP) connections with ChromeOS. I had extreme difficulties browsing webpages on the Chrombook. Some pages would load, some pages would not load at all. There seemed to be no consitency to it as some would load one day, but not another. Somewhere in the Google Groups there seemed to be people reporting issues with wireless connections using WEP. It turned out that the Wireless Modem Router (Telekom Austria supplied Pirelli PBS modem) where I was staying was set to WPA encryption only by default. Once I figured out how to set the unit to WPA2 (which these days should really be the default anyway) things started to actually work consistently. Check the sections below (specially chrome://diagnostics) to see how you can find out what's going wrong. However to save some trouble & frustrations, before you do anything make sure your Chrombook connects using WPA2 ! Terminal CTRL+ALT+T will launch the Chrome Shell which is a slightly odd and very cut-down…

Continue Reading