Hello Git Community. While using the Git tool on windows and a custom path for a private SSH (due to some policies and guidelines I've got to follow), I encountered a particular issue. I think this is related to a bug, I attach the template generated by git bugreport down below. Regards! Randall Alfaro
Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) R/ Set up GIT_SSH_COMMAND or core.sshCommand What did you expect to happen? (Expected behavior) R/ To be able to fetch/pull/push What happened instead? (Actual behavior) R/ "Disallowed command" was obtained by the server What's different between what you expected and what actually happened? R/ Any GIT command worked. Anything else you want to add: While debugging and troubleshooting, I noticed that the command "git-upload-pack" was getting sent two times. This is the command sent to the server after connecting to ssh (with -vvv) git-upload-pack '<PRIVATE PATH>' -o SendEnv=GIT_PROTOCOL -p <PRIVATE_PORT> git@<PRIVATE URL> git-upload-pack '<PRIVATE PATH>' After debugging as well the normal behavior when ssh is used but without GIT_SSH_COMMAND or core.sshCommand (by using the .ssh folder and config), the command is indeed only sent one time. My hypothesis is that this might be a bug, and sending the command two times might be causing GitLab to respond with the "Disallowed command" error. Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.35.2.windows.1 cpu: x86_64 built from commit: 518ccba2352ce721cabbbf2933869c3c3313d1c3 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 19042 compiler info: gnuc: 11.2 libc info: no libc information available $SHELL (typically, interactive shell): <unset> [Enabled Hooks]
