3/21/2023 0 Comments Gitextensions ssh proxy![]() I havent tried it myself but something like this might work: choco install gitextensions. Ssh.exe": hostPutty:path: no address associated with nameįatal: The remote end hung up unexpectedlyĮrror: cannot spawn "C:\tools\PuTTY\plink. What is the argument to install with OpenSSH Dan 5 years ago. I had %GIT_SSH% pointed to ssh.exe and used a host alias instead of path incl.If you don't do it this way, you might run into all kinds of problems like: Git clone you do that, Git and plink actually figure things out right! If the port is missing, and there's just a colon, Git treats it as a path separator, and ssh as the port delimiter (so they bite each fairly bad). Use the "full" command to pull, without any host aliases that would allow you to not specify the port, etc., in the example above. Set your environment variable %GIT_SSH% to point to plink.exe (it might be pointing to ssh.exe by default), make sure there aren’t apostrophes since the value will be used "as-is" (that's why you can't use spaces as stated above).Make sure plink.exe (the one available with GitExtensions or specifically installed with PuTTY) is in a path without spaces.Obviously make sure GitExtensions is set to use PuTTY, not OpenSSH.Do not use any host aliases you might have defined in file ~/.ssh/config.Do not create any sessions in PuTTY as outlined here.How do I combine all the parts to make them work?Īnd how come OpenSSH can deal with the problem, but PuTTY can't? The only problem with OpenSSH is that it keeps asking me for the password for the private key on every connection attempt (and I don't want to create a private key without a password). The bottom line ends up being the same though: Can't combine path to Git repository with a custom port. Let's call it "hostPutty", and set the default port there, etc. The right call to make would be plink -T -P 1234 I create an alias "hostCom" in my ~/.ssh/config, it seems to work correctly (connecting to #1234) if I just do this: plink -T as soon as I add the path to the Git repository too, it goes to #22 again.Īnother option I tried is to create a session in PuTTY. Note: Move the mouse over the blank area to generate randomness when generating. Step 1: Click on Tools -> Generate or Import Key. Using GitHub via HTTPS with Git Extensions can become pretty boring. I have a Git repository that I pull using a path similar to this: git pull GitExtensions then tries to pull from the repository using plink, it makes this call: plink -T ends up failing because it's actually pinging port #22, and not #1234. This step-by-step tutorial assumes that you have already installed Git Extensions on your computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |