Question

我正在尝试通过SSH从远程Gitlab服务器克隆存储库。我正在使用Gitlab CE version 9.3.9 755bb71和TortoiseGIT version 2.5.0以及git (for windows) version 2.14.0

正确安装了SSH密钥，因为我已使用

测试了身份验证

ssh -vT git@192.168.100.100 -i /path/to/.ssh/key

使用上面的密钥

，我收到以下有关身份验证成功的消息

OpenSSH_7.5p1, OpenSSL 1.0.2k  26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 192.168.100.100 [192.168.100.100] port 22.
debug1: Connection established.
debug1: identity file /path/to/.ssh/key type 1
debug1: key_load_public: No such file or directory
debug1: identity file /path/to/.ssh/key-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.5
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1
debug1: match: OpenSSH_6.6.1 pat OpenSSH_6.6.1* compat 0x04000000
debug1: Authenticating to 192.168.100.100:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:fEztD+bNxKRs24poXJMlP0GBAP6Q1dZT80OhQAtDQJE
debug1: Host '192.168.100.100' is known and matches the ECDSA host key.
debug1: Found key in /path/to/.ssh/known_hosts:1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /path/to/.ssh/key
debug1: Server accepts key: pkalg ssh-rsa blen 535
Enter passphrase for key '/path/to/.ssh/key':
debug1: Authentication succeeded (publickey).
Authenticated to 192.168.100.100 ([192.168.100.100]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: Remote: Forced command.
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Remote: Forced command.
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
Welcome to GitLab, John Doe!
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3476, received 3264 bytes, in 2.2 seconds
Bytes per second: sent 1574.0, received 1478.0
debug1: Exit status 0

当我在Windows上使用TortoiseGit克隆存储库时，我在客户端上收到以下错误

Cloning into 'C:\path\folder'...
GitLab: Disallowed command
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

在gitlab服务器上，gitlab-shell.log我收到以下警告信息

WARN -- : gitlab-shell: Attempt to execute disallowed command <git upload-pack '/path/to/repo.git'> by user with key key-1.

但是当我从另一台使用不同SSH密钥的Linux机器上尝试git clone时，它成功了，我在gitlab服务器上的gitlab-shell.log中收到以下信息消息

INFO -- : gitlab-shell: executing git command <gitaly-upload-pack  {"repository":{"path":"/very/long/path/to/repo.git"},"gl_id":"key-2"}> for user with key key-2.

我花了超过10个小时试图调试所有内容，但我不确定区别是什么或问题究竟在哪里。我还尝试在TortoiseGit的本地.gitconfig文件中添加以下内容，但这并没有改变任何内容。

[remote "origin"]
  uploadpack = git-upload-pack

最后，通过HTTPS克隆相同的存储库工作正常，使用用户名/密码没有任何问题。

Answer 1

注意：我刚刚升级到适用于Windows的Git 2.14.0 ...并且没有一个ssh网址正在运行：

> git ls-remote
GitLab: Disallowed command
fatal: Could not read from remote repository.

（origin是ssh网址）

另一个副作用：git-for-windows/git issue 1258

fatal: protocol error: bad line length character: Not

看起来BitBucket看起来好像argv[0]（通常是git-upload-pack，使用回归git）来确定它是否是允许的命令。

所以我认为设计git被拒绝而git-upload-pack不被拒绝。

GitLab上的错误相同：gitlab-ce issue 36028 pending merge request 在检测到git-xxx命令时显式恢复git xxx。

请参阅gitlab_shell.rb#parse_cmd(args)

  def parse_cmd(args)
    # Handle Git for Windows 2.14 using "git upload-pack" instead of git-upload-pack
    if args.length == 3 && args.first == 'git'
      @command = "git-#{args[1]}"
      args = [@command, args.last]
    else
      @command = args.first
    end

在Git for Windows端，正在进行修复：see commit 0f33428

还原＆＃34; git_connect：更喜欢Git的内置虚线格式＆＃34;

看起来这种变化（旨在修复测试   当git-upload-pack不在时，与本地存储库交互   PATH）对SSH访问感到退步。

Git for Windows 2.14.0(2) 正在进行中，并且在本次修改时30分钟前刚刚发布（2017-08-07T11：05：34Z UTC）。

原始答案

如果key1与您的/path/to/.ssh/key相同并且确定了John Doe，则表明John Doe无权访问该回购（as in here）。
检查key2是否与其他用户关联。

如果两个键都引用同一个用户，则更多的是本地配置问题（如this answer中所述）。还要检查您的TortoiseGit是否使用与测试中相同的密钥：

set "GIT_COMMAND_SSH=ssh -v"
# launch TortoiseGit from that CMD session

然后，您将看到TortoiseGit在使用ssh url克隆存储库时正在使用的内容。您可能需要define an .ssh/config file。

Answer 2

Bitbucket Server和Gogs都遇到了类似的问题。

似乎git 2.14.0（可能只在Windows上）发生了变化，需要更新产品或修复git。

无法在Windows上克隆，但可以从Gitlab服务器在Linux上克隆

2 个答案:

还原＆＃34; git_connect：更喜欢Git的内置虚线格式＆＃34;