SSH can’t be tunnelled through the HTTP proxy. And if I ever need to revoke access to my office machine I only need revoke that key from GitHub. The good thing about keys is that I can passphrase protect it so there’s something known only to me that I can type each time. If SSH works I could have used keys as usual. That’s because SSH won’t work through the proxy. Notice above that I am using HTTPS instead of SSH as is the norm. It’s a long piece of text and I’ll have to paste it in Notepad and copy paste into the command prompt each time I push. Did that and now I can push!īut that’s not very ideal as I don’t like storing the access token someplace. Turns out that’s because I use 2 factor authentication so I must create an access token. I am asked for a username/ password and while I am entering the correct details it keeps rejecting me: ![]() When I tried pushing though, I was stuck. This way I can pull repositories over https. I quickly created a shortcut with this and pinned to my taskbar so I can launch Cntlm whenever required (and it stays in the foreground, so closing the window will close Cntlm). When installing it creates a service and all, but you can run it by launching the exe file and pointing it to the config file. Your programs talk to Cntlm without any authentication Cntlm then talks to your proxy after proper authentication etc. (The config file takes password hashes instead of the plain text password). Its runs on your machine and authenticates with the proxy/ proxies you specify. Cntlm sits between the proxy and your software. That’s no dice for me though as there’s no way I am going to put my password in plain text anywhere! So I need a way around that.Įnter Cntlm. Proxy = http : / /mydomain \ \myusername :mypassword :8080Īpparently this only works with Basic authentication but since version 1.7.10 it works with NTLM authentication too (I didn’t test this).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |