Replies: 3 comments
|
感谢提供日志。我先确认了两个事实:
麻烦做一个最小对照测试:在该主机的「SSH 算法 → 高级算法配置」中分别只勾选下面各一项,保存后重连:
这组配置与您贴出的 Windows SSH 已经成功协商到的组合完全一致。请回复“能连接/仍然断开”,并附上这次的新调试日志。若能连接,我们就可以确定是 Netcatty 的默认协商顺序导致,并据此修复;若仍断开,则会继续单独验证客户端标识,避免改错方向。 |
0 replies
0 replies
|
尝试仅密码连接怎么样 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
连接报错如下图,但是mobaxterm直接连接正常

ssh的详细信息如下
C:\Users\lybing>ssh -v 192.168.1.254 -p 2222
OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2
debug1: Connecting to 192.168.1.254 [192.168.1.254] port 2222.
debug1: Connection established.
debug1: identity file C:\Users\lybing/.ssh/id_rsa type -1
debug1: identity file C:\Users\lybing/.ssh/id_rsa-cert type -1
debug1: identity file C:\Users\lybing/.ssh/id_ecdsa type -1
debug1: identity file C:\Users\lybing/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\Users\lybing/.ssh/id_ecdsa_sk type -1
debug1: identity file C:\Users\lybing/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file C:\Users\lybing/.ssh/id_ed25519 type -1
debug1: identity file C:\Users\lybing/.ssh/id_ed25519-cert type -1
debug1: identity file C:\Users\lybing/.ssh/id_ed25519_sk type -1
debug1: identity file C:\Users\lybing/.ssh/id_ed25519_sk-cert type -1
debug1: identity file C:\Users\lybing/.ssh/id_xmss type -1
debug1: identity file C:\Users\lybing/.ssh/id_xmss-cert type -1
debug1: identity file C:\Users\lybing/.ssh/id_dsa type -1
debug1: identity file C:\Users\lybing/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_9.5
debug1: Remote protocol version 2.0, remote software version OpenSSH
debug1: compat_banner: match: OpenSSH pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.254:2222 as 'lybing'
debug1: load_hostkeys: fopen C:\Users\lybing/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:6fxVGab7sKpCAQDP6qclNIfA+xLLYCsi8WYsX0T3DJw
debug1: load_hostkeys: fopen C:\Users\lybing/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts2: No such file or directory
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 ED25519 key sent by the remote host is
SHA256:6fxVGab7sKpCAQDP6qclNIfA+xLLYCsi8WYsX0T3DJw.
Please contact your system administrator.
Add correct host key in C:\Users\lybing/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in C:\Users\lybing/.ssh/known_hosts:17
Host key for [192.168.1.254]:2222 has changed and you have requested strict checking.
Host key verification failed.
netcatty的调试日志如下,尝试打开了网络设备模式,但是无效
1785228223443_1_netcatty-ssh.log
All reactions