Secure Shell (stable) updated to 0.40

[Mike Frysinger]

i've just released Secure Shell (stable) 0.40 [app/ext] which updates to OpenSSH 8.5p1.

Secure Shell (nassh) ChangeLog:

# 0.40, 2021-05-12, OpenSSH 8.5p1.

* l10n: Update translations.
* ssh_client: Upgrade to OpenSSH 8.5p1.
* crosh: Use nassh options page when non-SWA.
* crosh: Use terminalPrivate.openOptionsPage() if running as SWA.

-mike

[Nom De Plume]

Just need to say, thank you so much for the work you and the crew do on this and all the other projects.  

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOScmfsid9N3W6ktcQy2YHUw6fJBGXthUzxY%2Bgf2JunGsUDA%40mail.gmail.com.

[Chris Shelton]

Mike,

I also appreciate your great work on this extension that I use every day.  When upgrading to version 0.40, I noticed that I am seeing the following messages appear when connecting to either of the hosts that I normally use:

hostfile_replace_entries: mkstemp: Not a directory
update_known_hosts: hostfile_replace_entries failed for /.ssh/known_hosts: Not a directory
hostfile_replace_entries: mkstemp: Not a directory
update_known_hosts: hostfile_replace_entries failed for /.ssh/known_hosts2: Not a directory

This does not seem to affect my ability to establish the connection, as everything seems to work normally after starting up the connection.  This only started with the upgrade to version 0.40.

Chris

--

[Clarence Dold]

Same error messages here.

Version 90.0.4430.100 (Official Build) (32-bit) on a Lenovo C330 Chromebook.

Welcome to Secure Shell version 0.40.

...

hostfile_replace_entries: mkstemp: Not a directory

update_known_hosts: hostfile_replace_entries failed for /.ssh/known_hosts: Not a directory

hostfile_replace_entries: mkstemp: Not a directory

update_known_hosts: hostfile_replace_entries failed for /.ssh/known_hosts2: Not a directory

Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-73-generic x86_64)

[Mike Frysinger]

can you file a bug using the Send Feedback option in the extension ?  can't say i've seen this.

it'd help if you could describe the exact file config settings you're using (export via the options page and attach that json).

if you go into the options page and to the SSH Files section, is there anything in the known_hosts ?  if you click save, does the error go away ?

-mike

[Chris Shelton]

Mike,

I have just submitted this issue:

https://bugs.chromium.org/p/chromium/issues/detail?id=1208926

using the send feedback option in the extension.  I did attach a slightly edited version of my secure shell backup file, with the only changes made to obscure the hostnames of my ssh servers.  

The known_hosts section of the ssh file options panel does show entries for the 2 main ssh servers that I connect to, with their ecdsa-sha2-nistp256 format host keys.  I did remove one older entry that was no longer needed, and resaved the file.  This did not affect this minor issue.  

To clarify, this is a low priority issue, since it does not appear to cause any problems with the ssh connection, other than adding a bit of text to the screen when first starting the connection.

Chris

[Clarence Dold]

I opened https://bugs.chromium.org/p/chromium/issues/detail?id=1208990

I did obscure some portion of the json.

I am using  ssh keypairs ecdsa-sha2-nistp521

If the keypair is not saved (created a new connection to the same host, requiring a password) the errant messages don't appear.

--
Clarence A Dold - Santa Rosa, CA, USA

GPS: 38.47,-122.66, QTH CM88ql 
Claren...@Gmail.com

[Mike Frysinger]

OpenSSH 8.5 has turned on hostkey updating by default.  you can silence the warnings by adding to your ssh command line:

-oUpdateHostKeys=no

-mike

[Clarence Dold]

-oUpdateHostKeys=no
eliminated that error message for me.

--
Clarence A Dold - Santa Rosa, CA, USA

GPS: 38.47,-122.66, QTH CM88ql 
Claren...@Gmail.com

[Clarence Dold]

-oUpdateHostKeys=no
eliminated the error on the first host I tried, but I didn't replicate the error first.
A different host, without the option, gave no error.
Removing the line from the first host did not restore the error.

I closed all session and restarted Chrome without the option, still no error.

--
Clarence A Dold - Santa Rosa, CA, USA

GPS: 38.47,-122.66, QTH CM88ql 
Claren...@Gmail.com

[Ian Barkley-Yeung]

I'm getting consistent, repeated sad tab crashes when trying to connect to root@mycrbook. It always crashes when I type the first character of the password

It just started late last week, so I'd guess the new version was responsible.

https://listnr.corp.google.com/report/88558486826

https://listnr.corp.google.com/report/88550037496

https://listnr.corp.google.com/report/88550020494

https://listnr.corp.google.com/report/88550005777

Lots of crashes with the signature [Renderer kill] password_manager::bad_message::`anonymous namespace'::ReceivedBadMessage. Example: https://crash.corp.google.com/browse?q=ReportID%3D%276fdedb91ee41f54f%27&stbtiq=&reportid=&index=0. The signature started spiking on Chrome_ChromeOS on May 14th. 

[Mike Frysinger]

it appears to be a bug in Chrome

https://crbug.com/1208994

-mike

[Mike Webb]

Mike, I am also getting:

hostfile_replace_entries: mkstemp: Not a directory

update_known_hosts: hostfile_replace_entries failed for /.ssh/known_hosts: Not a directory

hostfile_replace_entries: mkstemp: Not a directory

update_known_hosts: hostfile_replace_entries failed for /.ssh/known_hosts2: Not a directory

xkbcommon: ERROR: Key "<CAPS>" added to modifier map for multiple modifiers; Using Mod3, ignoring Lock

Apart from this the connection still works and no side effects seen.

cheers

Mike W

[Clarence Dold]

This only happened for me on hosts with keys. Password logins were okay.
Adding the option on a connection with keys:

-oUpdateHostKeys=no
eliminated the error on the first host I tried. None of the other hosts with keys showed the error any more.

Removing the line from the first host did not restore the error.

--
Clarence A Dold - Santa Rosa, CA, USA

GPS: 38.47,-122.66, QTH CM88ql 
Claren...@Gmail.com

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/6f499201-f2da-447e-84bb-97d99782e3e7n%40chromium.org.