5 ms·
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 de
by kazinator 7y ago
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.
https://cygwin.com/pipermail/cygwin/2020-April/244384.html https://cygwin.com/pipermail/cygwin/2020-April/244384.html
- dallbee 7y agoDo be careful doing this, if your company cares, a competent network admin can tell what's going on.
- shawnz 7y agoYou can defeat deep packet inspection by tunneling it over an HTTPS proxy, using the SSH ProxyCommand option and the proxytunnel utility
- varenc 7y agoA corporate IT admin would probably detect this by pulling information directly from the company managed machines. i.e. osquery https://www.metalliccode.com/detecting-ssh-tunnels https://www.metalliccode.com/detecting-ssh-tunnels
- yownie 7y agoor just sshuttle
- shawnz 7y agoSshuttle solves a different problem. It uses SSH as a transport so it could not bypass a firewall that blocks outgoing SSH.
- LilBytes 7y agoWe had a sys. admin who did exactly this to access his home computer to play World of Tanks. :) 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.
- Jedd 7y agoI worked for an organisation that decided to stop outbound SSH for reasons that weren't adequately well explained, exceptions were painful to get re-applied, so most people just cranked up corkscrew and did precisely this. Only challenge is that getting corkscrew compiled on Windows is a massive pain. [n] https://github.com/bryanpkc/corkscrew https://github.com/bryanpkc/corkscrew
- kazinator 7y agoThe core API's of Windows are so stable that if someone got it working once on WIndows NT, the executable should work for everyone on Windows 2000, Windows XP, Windows Vista, Windows 7, 8 and 10, ...
- Jedd 7y agoYup - one of my smarter colleagues had a go at getting it compiled on Windows, and basically gave it up as the library dependencies were such a mess on that platform. No one seems to have packaged up binaries for it either.
- saagarjha 7y agoTrying to defeat measures that your corporate IT department has put up sounds like an excellent way to be terminated.
- varenc 7y agoAt a large company, I imagine IT would be concerned about this setup. Though it’s on them to make the proper VPN solution more usable. Hacking your home domain would give someone a powerful jumping off point for hacking other things on your corporate network.
- kazinator 7y agoLess of a surface than in the scenario that the home domain is hacked and there is VPN running.
- varenc 7y agoWell, if IT is running a tight ship then only corporate owned/managed machines can access the VPN and not a home domain. Those machines might be just as hackable, but they should at least have some logging in place that allow detection or postmortem analysis.
- MaxBarraclough 7y agoThat's likely to be a firing offence, no? If I were running things I wouldn't want employees deliberately subverting my network's security measures in the name of their own convenience. If you have to spend time wrestling the VPN while you're on the clock, that's their own time being wasted.
- deleted 7y ago[deleted]
- kazinator 7y agoAll you would have to do is disallow outbound SSH.
- MaxBarraclough 7y agoSure, but if you break your employer's cybersecurity policies, you don't get to blame IT for failing to prevent you from doing it.
- kazinator 7y agoUsing outbound SSH when that is allowed is compliance with cybersecurity policy.
- acdha 7y agoThat's tricky, though, since there are many uses for SSH which are not circumventing security policy — blocking outbound SSH would also mean you couldn't use Git, manage servers in the cloud or other locations, transfer files, etc. 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.
- kazinator 7y ago> blocking outbound SSH would also mean you couldn't use Git, manage servers in the cloud or other locations, transfer files, etc. 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?