Unable to negotiate with UNKNOWN port -1: no matching host key type found. Their offer: ssh-dss

1,454 views
Skip to first unread message

Mike Acton

unread,
Apr 11, 2017, 8:06:49 PM4/11/17
to chromium-hterm
Secure Shell (dev) version 0.8.36.1
Recently unable to connect to a server I have been previously connecting to without issues. (Server has not been changed.)

Getting error:
Unable to negotiate with UNKNOWN port -1: no matching host key type found. Their offer: ssh-dss

I didn't see anyone else on the list having this issue reported after a quick search, so I assume something on my end /somewhere/ must have changed - but I'm not sure what it could have been. 
Looking for any guidance/tips for what to look into.

Server is Bitvise SSH server running on Windows 10.
I can still connect to server with other ssh clients.



Brandon Gilmore

unread,
Apr 11, 2017, 8:14:52 PM4/11/17
to Mike Acton, chromium-hterm
You can try adding -oHostKeyAlgorithms=+ssh-dss to the "SSH Arguments" field to re-enable DSA algorithm.

Note that this is disabled by default by OpenSSH 7.0+ because DSA is considered to be weak and its use may be fundamentally insecure.

I'm not familiar with Bitvise, but ideally you'd be able to generate a host key using a secure key algorithm (e.g. RSA, ECDSA) and this flag wouldn't be required.

--
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-hterm+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAGxtOJawHkt45xr-da5CHwjbwEhheqcG69AO6y%2BfLE1FM7wFhQ%40mail.gmail.com.

Mike Frysinger

unread,
Apr 11, 2017, 8:18:11 PM4/11/17
to Mike Acton, chromium-hterm, Brandon Gilmore
Brandon is obviously correct.  i'll update the ChangeLog/FAQ to make note of it.
-mike

Mike Acton

unread,
Apr 11, 2017, 9:01:14 PM4/11/17
to Mike Frysinger, chromium-hterm, Brandon Gilmore
Thank you. Yes, that solves the problem.

(ssh security is a non-issue in my scenario. Telnet would be sufficient. But I'd have to continue to maintain a separate extension/app...)


Message has been deleted

Mike Frysinger

unread,
Apr 22, 2018, 12:35:59 PM4/22/18
to rafael....@gmail.com, chromium-hterm
there is no support for passing arbitrary options in the ssh:// URI specification

you can star https://crbug.com/217785 for updates
-mike

On Fri, Apr 13, 2018 at 6:46 AM <rafael....@gmail.com> wrote:
It works when creating a new conection, but if a use an URL wich is my real need it doesnt, I'm  writing in the URL ling on my web page something like this:

ssh://user...@1.2.3.4%20-oHostKeyAlgorithms%3D%2Bssh-dss

Is there another way to pass parameters, what I'm doing wrong

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
Reply all
Reply to author
Forward
0 new messages