Secure Shell (dev) 0.8.36.0 released

79 views
Skip to first unread message

Mike Frysinger

unread,
Mar 31, 2017, 5:51:36 PM3/31/17
to chromium-hterm
i've just released Secure Shell (dev) 0.8.36.0 which upgrades openssh to 7.5p1 and culls some dead/obsolete JS code.  you should be able to access systems using ECDSA/ED25519 keys now.  woo!

the downside is that the NaCl files have grown a bit (about 1.5MB per .nexe).  i have a change in flight to only release stripped versions though which should cut the sizes significantly, so look for that in a future release.

# 0.8.36.0, 2017-03-31, cleanup + openssh upgrade.

* Upgraded openssh from 6.6p1 to 7.5p1.  Notably, support for ECDSA/ED25519.
* Fixed handling of errno values in NaCl plugin for clearer errors.
* Auto register ourselves as ssh:// protocol handler.
* Add protip for ctrl+clicking links to startup message.
* Cleanup obsolete CSS variable hacks.
* Drop support for Chrome <22 versions.
* Drop wash hooks from the manifest.
-mike


Hendrik van Niekerk

unread,
Apr 1, 2017, 5:12:27 PM4/1/17
to chromium-hterm
After this upgrade I cannot log in to a server using a public key pair.  I get the following messages:

Connecting to xx...@xxxxxxxxx.xxx...
Loading NaCl plugin... done.
Load key "/.ssh/id_rsa": file changed while reading
Permission denied (publickey).
NaCl plugin exited with status code 255.

I've removed all keys and reloaded - this makes no difference.  I also see the same error when trying to mount SFTP 

Hennie

Chris Shelton

unread,
Apr 1, 2017, 8:39:17 PM4/1/17
to chromium-hterm
I'm also getting this error too. I did have to update chromeos in order to install this version, so not sure which was the cause in my case

Gerad Munsch

unread,
Apr 1, 2017, 10:46:21 PM4/1/17
to chromium-hterm
I am seeing the same error, as well.

I tried the same steps as Hendrik, removing my keys, killing all instances of the extension, readding them, to no avail.

Additionally, I (temporarily) switched back to "tab" mode (from "window" mode), and watched the JS console (set to verbose) and network tab while attempting connection(s), and did not see any pertinent information as to what's occurring to cause the error.

Looking forward to a fix, as I use SSH on my Chromebook daily.

Thanks for the awesome work, chromium team!

--
Gerad Munsch


On Friday, March 31, 2017 at 4:51:36 PM UTC-5, Mike Frysinger wrote:
Message has been deleted

Mike Frysinger

unread,
Apr 3, 2017, 5:37:38 PM4/3/17
to Hendrik van Niekerk, chromium-hterm
looks like a bug in upstream openssh that our ppapi FS stubs tickled.  we probably should make our stat logic a bit more full featured, but openssh should also not be buggy :).

for future reference, please file bug reports using crbug.com/new.  i've moved this to https://crbug.com/707941.
-mike

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/76ea5211-5cbc-4450-a28a-3d94ff5232e8%40chromium.org.

Mike Frysinger

unread,
Apr 3, 2017, 9:35:36 PM4/3/17
to Hendrik van Niekerk, cmsh...@gmail.com, unforg...@gmail.com, chromium-hterm
this is fixed in the 0.8.36.1 release
-mike
Reply all
Reply to author
Forward
0 new messages