Closed hktalent closed 7 years ago
Seems like what ever cipher your server is negotiating is not available on the client. You can set cipher strings on the .connect
event in index.js
file around line 125-129. master branch has these set to work with some Cisco routers that have trouble negotiating higher cipher strengths. exec-test branch has this commented out.
This is not as much an issue with WebSSH2 as it is providing the proper cipher strings to pass to the ssh2 module by @mscdex
Check out that page for the proper cipher settings. You can also enable debug mode in both your sshd on the server side as well as ssh2 here by adding a debug function to the .connect
event in index.js.
}).connect({
host: config.ssh.host,
port: config.ssh.port,
username: config.user.name,
password: config.user.password,
debug: console.log,
tryKeyboard: true
});
client os
mac 10.12.3 uname -a Darwin QQ1160.local 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64
1.safari ver 10.0.3 (12602.4.8)
http://localhost:2222/ssh/host/192.168.10.243
2.server: name -a
Linux kali 4.6.0-kali1-amd64 #1 SMP Debian 4.6.4-1kali1 (2016-07-21) x86_64 GNU/Linux
3.error
kali linux out error SSH CONNECTION CLOSE - Error: Handshake failed: no matching client->server cipherError: read ECONNRESETError: Handshake failed: no matching client->server cipherError: read ECONNRESET CREDENTIALS
in chrome 56.0.2924.87 (64-bit) SSH CONNECTION CLOSE - Error: Handshake failed: no matching client->server cipherError: read ECONNRESETError: Handshake failed: no matching client->server cipherError: read ECONNRESETError: Handshake failed: no matching client->server cipherError: read ECONNRESETError: Handshake failed: no matching client->server cipher CREDENTIALS
node index.js
console
kali linux
uname -a Linux kali 4.6.0-kali1-amd64 #1 SMP Debian 4.6.4-1kali1 (2016-07-21) x86_64 GNU/Linux
other linux is ok
uname -a Linux appserver 2.6.32-279.el6.x86_64 #1 SMP Thu Jun 21 15:00:18 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux