My favorite SSH trick is to have a machine at work SSH back to my home domain, and provide a tunnel back for Remote Desktop or what have you.
Wee, no VPN to deal with. No lack of a VPN for remote access to deal with.
Wee, no VPN to deal with. No lack of a VPN for remote access to deal with.
If you have to spend time wrestling the VPN while you're on the clock, that's their own time being wasted.
Using this to circumvent policy is exactly the kind of move which would lead to those other uses being banned and making life worse for all of your coworkers.
That's right, and that's how it is with my current employer.
If you need outbound SSH to work with Git, that probaly means you're working on a side project, not work. Fetching public code needed for work from a hosting site can be done over https.
Managing servers in the cloud, ditto. If managing servers in the cloud isn't part of your job description, why would your workplace enable that?
But I agree that it's not a good idea to poke holes in your corporate firewall (which is really what this is doing).
Hacking your home domain would give someone a powerful jumping off point for hacking other things on your corporate network.
He still works there in a Government Agency riddled with staff who are perfectly adapt at doing enough to stay hired and doing little enough to describe their job as a paid hobby.
Only challenge is that getting corkscrew compiled on Windows is a massive pain.
No one seems to have packaged up binaries for it either.
Is that good enough support?
We tried.
MinGW refers to headers from BSD sockets, which doesn't exist on windows.