Thanks for the reply!
I would fix that bit if I could, but it's more a policy issue...
Wouldn't I need something like an http-Proxy running on Windows?
As far as I understand, if I could create a tunnel from the Windows machine to the git server I could make it visible to the Linux machine, but with one from Windows to Linux? How would I do that?
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
You can use ssh to create a reverse tunnel. The Windows machine starts the ssh session, and forwards a port on the Linux box to the external git server (or itself if you're using a bare repo on the Windows machine). Then from the linux machine you set the git remote to be "localhost" and as far as Linux is concerned the git server is running locally.
Thanks for the reply!
I would fix that bit if I could, but it's more a policy issue...
Wouldn't I need something like an http-Proxy running on Windows?
As far as I understand, if I could create a tunnel from the Windows machine to the git server I could make it visible to the Linux machine, but with one from Windows to Linux? How would I do that?
You can use ssh to create a reverse tunnel. The Windows machine starts the ssh session, and forwards a port on the Linux box to the external git server (or itself if you're using a bare repo on the Windows machine). Then from the linux machine you set the git remote to be "localhost" and as far as Linux is concerned the git server is running locally.
Thanks. I guess I didn't know that you could tunnel a port that is neither on the ssh client or server machine.