【问题标题】:SSH working on cmd but not on Git Bash (Windows 10)SSH 在 cmd 上工作,但在 Git Bash 上不工作(Windows 10)
【发布时间】:2022-07-05 19:06:30
【问题描述】:

SSH 以前可以很好地与 Git Bash 配合使用。不知道最近发生了什么。

CMD 上的 SSH 版本:

C:\Users\ my-user>ssh -V
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2

CMD 上的调试/错误:

C:\Users\ my-user>ssh -V
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2

C:\Users\ my-user>ssh -v my-user1@server-url
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Connecting to server-url [public-ip] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\ my-user/.ssh/id_rsa type 0
debug1: identity file C:\\Users\\ my-user/.ssh/id_rsa-cert type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_dsa type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_dsa-cert type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_ecdsa type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_ed25519 type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_ed25519-cert type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_xmss type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
debug1: match: OpenSSH_7.4 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to server-url:22 as 'my-user1'
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: Server host key: ssh-ed25519 SHA256:Mw4Mlvqk2MgCynA+8nTUrxDy8wxXONlTAVk2K/FgbcQ
debug1: Host 'server-url' is known and matches the ED25519 host key.
debug1: Found key in C:\\Users\\ my-user/.ssh/known_hosts:167
debug1: rekey out after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 4294967296 blocks
debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_rsa RSA SHA256:OyvnNnesOb+dn3j9NWl9dkDu/Fi52CKlN9Vq8h9LzoA
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_dsa
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_ecdsa
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_ed25519
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug1: SSH2_MSG_SERVICE_ACCEPT received
Authorized uses only. All activity may be monitored and reported.
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic
debug1: Next authentication method: publickey
debug1: Offering public key: C:\\Users\\ my-user/.ssh/id_rsa RSA SHA256:OyvnNnesOb+dn3j9NWl9dkDu/Fi52CKlN9Vq8h9LzoA
debug1: Server accepts key: C:\\Users\\ my-user/.ssh/id_rsa RSA SHA256:OyvnNnesOb+dn3j9NWl9dkDu/Fi52CKlN9Vq8h9LzoA
debug1: Authentication succeeded (publickey).
Authenticated to server-url ([public-ip]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: ENABLE_VIRTUAL_TERMINAL_INPUT is supported. Reading the VTSequence from console
debug1: ENABLE_VIRTUAL_TERMINAL_PROCESSING is supported. Console supports the ansi parsing
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
Last login: Tue Jun 28 09:20:50 2022 from org-ip

在 Git Bash 上使用相同的 SSH 版本:

 my-user@my-server MINGW64 /
$ ssh -V
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2

Git Bash 上的调试/错误:

 my-user@my-server MINGW64 /
$ ssh -v my-user1@server-url
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
Pseudo-terminal will not be allocated because stdin is not a terminal.
debug1: Connecting to server-url [public-ip] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\ my-user/.ssh/id_rsa type 0
debug1: identity file C:\\Users\\ my-user/.ssh/id_rsa-cert type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_dsa type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_dsa-cert type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_ecdsa type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_ed25519 type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_ed25519-cert type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_xmss type -1
debug1: identity file C:\\Users\\ my-user/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
debug1: match: OpenSSH_7.4 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to server-url:22 as 'my-user1'
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: Server host key: ssh-ed25519 SHA256:Mw4Mlvqk2MgCynA+8nTUrxDy8wxXONlTAVk2K/FgbcQ
debug1: Host 'server-url' is known and matches the ED25519 host key.
debug1: Found key in C:\\Users\\ my-user/.ssh/known_hosts:167
debug1: rekey out after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 4294967296 blocks
debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_rsa RSA SHA256:OyvnNnesOb+dn3j9NWl9dkDu/Fi52CKlN9Vq8h9LzoA
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_dsa
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_ecdsa
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_ed25519
debug1: Will attempt key: C:\\Users\\ my-user/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug1: SSH2_MSG_SERVICE_ACCEPT received
Authorized uses only. All activity may be monitored and reported.
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic
debug1: Next authentication method: publickey
debug1: Offering public key: C:\\Users\\ my-user/.ssh/id_rsa RSA SHA256:OyvnNnesOb+dn3j9NWl9dkDu/Fi52CKlN9Vq8h9LzoA
debug1: Server accepts key: C:\\Users\\ my-user/.ssh/id_rsa RSA SHA256:OyvnNnesOb+dn3j9NWl9dkDu/Fi52CKlN9Vq8h9LzoA
debug1: Authentication succeeded (publickey).
Authenticated to server-url ([public-ip]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
<gets stuck here> 

欢迎任何帮助/线索 注意:Git Bash 使用 mintty 终端

【问题讨论】:

  • 找到了一个解决方法:如果我选择“Windows cmd”作为终端而不是“mintty”,这是安装时的默认设置,SSH 可以工作。

标签: ssh cmd windows-10 git-bash mintty


【解决方案1】:

找到了一个变通的解决方案:如果我选择“Windows cmd”作为终端而不是“mintty”,这是安装时的默认设置,SSH 可以工作

【讨论】:

    猜你喜欢
    • 2020-01-04
    • 1970-01-01
    • 1970-01-01
    • 2016-05-19
    • 2022-01-20
    • 2019-02-09
    • 1970-01-01
    • 2016-09-09
    • 2017-08-05
    相关资源
    最近更新 更多