为准备好做我的第一次而感到兴奋git push曾经，我为PuTTY在我的 cygwin 环境中：
alias ssh="/cygdrive/c/PROGRA~2/putty/PUTTY.EXE"
然后调用（当然是在我的工作目录中），正如第 47 页中所述git 社区书籍:
git push ssh://mylinuxserver/~winwin/gitrepo master:master
我的兴奋并没有持续多久，因为它立即失败并出现致命错误：
error: cannot run ssh: No such file or directory
fatal: unable to fork
考虑到我能够成功运行，来自相同的命令行和 shell 实例, ssh winwin@mylinuxserver收到此错误消息我感到非常惊讶。
知道为什么会发生这种情况以及如何解决这个问题吗？
更新一：谢谢本指南，我发现 PUTTY.EXE 不是在 git 中使用的正确 exe。相反，人们应该使用链接程序.
该指南还暗示应该使用名为 GIT_SSH 的环境变量来让 git 知道如何发挥作用。所以我：
~/sb/ws> export GIT_SSH=/cygdrive/c/PROGRA~2/putty/PLINK.EXE
~/sb/ws> git push ssh://mylinuxserver/~winwin/gitrepo master:master
现在我收到一个不同的错误：
fatal: The remote end hung up unexpectedly
我认为这个进展是正确的，但我仍然不知道如何解决问题。任何想法将不胜感激。
更新二：仍在努力解开这个谜团。这次我怀疑自从git push不会在任何地方提示输入用户名+密码，身份验证必须位于密钥内......所以，我仔细检查了sshd配置每这个指南。我发现唯一需要更改的是取消注释该行HostKey /etc/ssh/ssh_host_dsa_key in /etc/ssh/sshd_config并重新启动服务service sshd restart。在那之后的第一次，$GIT_SSH确实提示确认服务器的 dss 密钥指纹，并且我确认将密钥存储在缓存中，但是......问题仍然存在：
fatal: The remote end hung up unexpectedly
其他想法？
（PuTTY 的注册表现在包含同一服务器的两个密钥：rsa2@22:mylinuxserver and dss@22:mylinuxserver。嗯......我不确定这意味着什么）
更多诊断信息： Typing $GIT_SSH -v yields:
~/sb/ws> $GIT_SSH -v
Looking up host "mylinuxserver"
Connecting to 192.168.1.2 port 22
Server version: SSH-2.0-OpenSSH_4.2
We claim version: SSH-2.0-PuTTY_Release_0.60
Using SSH protocol version 2
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-1
Host key fingerprint is:
ssh-dss 1024 c8:77:42:4f:76:29:56:4c:ea:b0:11:6a:a6:3c:6a:f7
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA1 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA1 server->client MAC algorithm
login as: winwin
winwin@mylinuxserver's password:
Sent password
Access granted
Opened channel for session
Allocated pty (ospeed 38400bps, ispeed 38400bps)
Started a shell/command
Last login: Wed Jul 13 21:41:12 2011 from winmachine
你能发现任何可疑的地方吗？
到达那里：到目前为止，适合我的情况的最佳指南：git、SSH、腻子.
见解：
-
$GIT_SSH -agent必须运行一次
- PAGEANT.EXE 必须在后台运行（并且通过其私钥添加到它）系统托盘图标!)
- 必须使用 PUTTYGEN.EXE 生成公钥/私钥对
- dss不是强制性的，rsa就足够了。
-
More？ （除非
$GIT_SSH -2 -C -i C:\\Users\\winwin\\SSH\\private.ppk在没有密码提示的情况下成功，没有必要尝试git push...)
将公钥从 PuTTY 密钥生成器复制并粘贴到/home/winwin/.ssh/authorized_keys in mylinuxserver一条新消息出现以响应上面见解 #5 中的命令：
Server refused our key
这是一个好兆头...:)我想我正在解开这个谜团。
更新三：改变后StrictModes to no in /etc/ssh/sshd_config在 sshd 服务器上，我成功了$GIT_SSH -2 -C -i C:\\Users\\winwin\\SSH\\private.ppk。但它仍然提示输入用户名（但不提示输入密码）。
git push ssh://mylinuxserver/~winwin/gitrepo master:master但是仍然失败 - 并显示相同的错误消息：
fatal: The remote end hung up unexpectedly
疯了吧。
更新四： The -l usernamePLINK 的参数是关键。我设法使git push通过创建1行shell脚本登录成功/cygdrive/c/PROGRA~2/putty/PLINK.EXE -l winwin $*并将整个脚本的路径导出到$GIT_SSH，但“远端仍然意外挂断”。
这是我在客户端 (Windows/PuTTY) 端得到的信息：
~/sb/ws> git push ssh://mylinuxserver/~winwin/gitrepo master:master
Environment:
USER=winwin
LOGNAME=winwin
HOME=/home/winwin
PATH=/usr/local/bin:/bin:/usr/bin
MAIL=/var/mail/winwin
SHELL=/bin/bash
SSH_CLIENT=192.168.1.8 50951 22
SSH_CONNECTION=192.168.1.8 50951 192.168.14.2 22
bash: mylinuxserver: command not found
fatal: The remote end hung up unexpectedly
这就是我在服务器端（Linux/sshd）端得到的：
debug1: sshd version OpenSSH_4.2p1
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
debug1: Bind to port 22 on 0.0.0.0.
Bind to port 22 on 0.0.0.0 failed: Address already in use.
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7
debug1: inetd sockets after dupping: 3, 3
Connection from 192.168.1.8 port 50951
debug1: Client protocol version 2.0; client software version PuTTY_Release_0.60
debug1: no match: PuTTY_Release_0.60
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.2
debug1: permanently_set_uid: 74/74
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: client->server aes256-ctr hmac-sha1 none
debug1: kex: server->client aes256-ctr hmac-sha1 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD received
debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
debug1: userauth-request for user winwin service ssh-connection method none
debug1: attempt 0 failures 0
debug1: PAM: initializing for "winwin"
debug1: PAM: setting PAM_RHOST to "win7client"
debug1: PAM: setting PAM_TTY to "ssh"
Failed none for winwin from 192.168.1.8 port 50951 ssh2
debug1: userauth-request for user winwin service ssh-connection method publickey
debug1: attempt 1 failures 1
debug1: test whether pkalg/pkblob are acceptable
debug1: temporarily_use_uid: 513/513 (e=0/0)
debug1: trying public key file /home/winwin/.ssh/authorized_keys
debug1: matching key found: file /home/winwin/.ssh/authorized_keys, line 1
Found matching RSA key: bd:a6:4a:6a:04:43:8d:60:d9:bf:66:de:51:13:83:66
debug1: restore_uid: 0/0
Postponed publickey for winwin from 192.168.1.8 port 50951 ssh2
debug1: userauth-request for user winwin service ssh-connection method publickey
debug1: attempt 2 failures 1
debug1: temporarily_use_uid: 513/513 (e=0/0)
debug1: trying public key file /home/winwin/.ssh/authorized_keys
debug1: matching key found: file /home/winwin/.ssh/authorized_keys, line 1
Found matching RSA key: bd:a6:4a:6a:04:43:8d:60:d9:bf:66:de:51:13:83:66
debug1: restore_uid: 0/0
debug1: ssh_rsa_verify: signature correct
debug1: do_pam_account: called
Accepted publickey for winwin from 192.168.1.8 port 50951 ssh2
debug1: monitor_child_preauth: winwin has been authenticated by privileged process
Accepted publickey for winwin from 192.168.1.8 port 50951 ssh2
debug1: PAM: reinitializing credentials
debug1: permanently_set_uid: 513/513
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: server_input_channel_open: ctype session rchan 256 win 16384 max 16384
debug1: input_session_request
debug1: channel 0: new [server-session]
debug1: session_new: init
debug1: session_new: session 0
debug1: session_open: channel 0
debug1: session_open: session 0: link with channel 0
debug1: server_input_channel_open: confirm session
debug1: server_input_channel_req: channel 0 request exec reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req exec
debug1: Received SIGCHLD.
debug1: session_by_pid: pid 3441
debug1: session_exit_message: session 0 channel 0 pid 3441
debug1: session_exit_message: release channel 0
debug1: session_close: session 0 pid 3441
debug1: channel 0: free: server-session, nchannels 1
Connection closed by 192.168.1.8
debug1: do_cleanup
debug1: PAM: cleanup
Closing connection to 192.168.1.8
debug1: PAM: cleanup
需要最后一条线索...
- 什么是
bash: mylinuxserver: command not found mean?
- What is
git push试图逃跑？
- 哪个命令？
- 在客户端还是 SSH 服务器上？
