Re: How to see command line arguments passed to program in core.sshcommand?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/22/2019 11:17 PM, Jeffrey Walton wrote:
> Hi Everyone,
> 
> I'm working in an unusual setup on WIndows. I need to 'git clone' over
> SSH, but a third party program has to handle the tunnel. It happens by
> using this git configuration:
> 
>     git config --global core.sshcommand "tunnel.exe ... <path-to-public-key>"
> 
> After I execute the 'git config' command, I open ~/.gitconfig and
> ensure the path is correct and quoted per Windows standards.
> 
> So far the result has been a failed authentication, which seems to
> indicate something went sideways using the public key. I don't receive
> an error from Git or or the tunnel program relating to a "file not
> found" (or any errors for that matter until authentication fails).
> 
> I need to spy the command line arguments being passed around, but I
> have not been able to do so. 'git clone -verbose' is ineffective, and
> -vvv is rejected as an unknown option.
> 
> How do I see command line arguments passed to the program in core.sshcommand?

Have you tried GIT_TRACE=1 or GIT_TRACE2=1? Both options should record
a log entry for any spawned processes.

(You can also point these to fully-qualified filenames.)

Thanks,
-Stolee



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux