News for hackers. Stuff that matters.
Re:SSH hacks – a little sanity for remote workers by kazinator on Wednesday April 29, 2020 @09:24PM (#23026535)
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

Re:SSH hacks – a little sanity for remote workers by MaxBarraclough on Thursday April 30, 2020 @05:04AM (#23028900)
That'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.

Re:SSH hacks – a little sanity for remote workers by packetslave on Friday May 01, 2020 @10:07PM (#23048477)
Maybe not a firing offense, but if you ran 'ssh -R' at $JOB-1, you'd pretty much immediately have someone from the security ops team messaging you to ask what you're up to.
Re:SSH hacks – a little sanity for remote workers by kazinator on Thursday April 30, 2020 @09:46AM (#23030732)
All you would have to do is disallow outbound SSH.
Re:SSH hacks – a little sanity for remote workers by acdha on Thursday April 30, 2020 @02:37PM (#23034429)
That'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.

Re:SSH hacks – a little sanity for remote workers by kazinator on Thursday April 30, 2020 @04:39PM (#23035821)
> 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?

Re:SSH hacks – a little sanity for remote workers by MaxBarraclough on Thursday April 30, 2020 @12:32PM (#23032772)
Sure, but if you break your employer's cybersecurity policies, you don't get to blame IT for failing to prevent you from doing it.
Re:SSH hacks – a little sanity for remote workers by kazinator on Thursday April 30, 2020 @04:34PM (#23035770)
Using outbound SSH when that is allowed is compliance with cybersecurity policy.
Re:SSH hacks – a little sanity for remote workers by m463 on Thursday April 30, 2020 @05:47PM (#23036554)
That would be cat and mouse. You can ssh on any port.

But I agree that it's not a good idea to poke holes in your corporate firewall (which is really what this is doing).

Re:SSH hacks – a little sanity for remote workers by kazinator on Thursday April 30, 2020 @06:33PM (#23037013)
If you think that's poking holes in the firewall, you should see this javascript stuff that worms itself back over most of your HTTPS connections from countless third-party sites.
Re:SSH hacks – a little sanity for remote workers by varenc on Wednesday April 29, 2020 @09:41PM (#23026625)
At 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.

Re:SSH hacks – a little sanity for remote workers by kazinator on Thursday April 30, 2020 @09:45AM (#23030723)
Less of a surface than in the scenario that the home domain is hacked and there is VPN running.
Re:SSH hacks – a little sanity for remote workers by varenc on Monday May 04, 2020 @05:04PM (#23073229)
Well, 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.
Re:SSH hacks – a little sanity for remote workers by dallbee on Wednesday April 29, 2020 @09:36PM (#23026597)
Do be careful doing this, if your company cares, a competent network admin can tell what's going on.
Re:SSH hacks – a little sanity for remote workers by shawnz on Wednesday April 29, 2020 @09:40PM (#23026622)
You can defeat deep packet inspection by tunneling it over an HTTPS proxy, using the SSH ProxyCommand option and the proxytunnel utility
Re:SSH hacks – a little sanity for remote workers by varenc on Wednesday April 29, 2020 @09:48PM (#23026659)
A 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

Re:SSH hacks – a little sanity for remote workers by Jedd on Wednesday April 29, 2020 @11:04PM (#23027046)
I 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

Re:SSH hacks – a little sanity for remote workers by kazinator on Thursday April 30, 2020 @04:47PM (#23035907)
The 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, ...
Re:SSH hacks – a little sanity for remote workers by Jedd on Friday May 01, 2020 @01:37AM (#23039411)
Yup - 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.

Re:SSH hacks – a little sanity for remote workers by mycall on Friday May 08, 2020 @06:06PM (#23120074)
> Win32 (with Cygwin)

Is that good enough support?

Re:SSH hacks – a little sanity for remote workers by Jedd on Saturday May 09, 2020 @05:15AM (#23123257)
Are you saying that's an environment in which you can compile it?

We tried.

MinGW refers to headers from BSD sockets, which doesn't exist on windows.

Re:SSH hacks – a little sanity for remote workers by LilBytes on Wednesday April 29, 2020 @10:29PM (#23026888)
We 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.

Re:SSH hacks – a little sanity for remote workers by saagarjha on Thursday April 30, 2020 @02:57PM (#23034679)
Trying to defeat measures that your corporate IT department has put up sounds like an excellent way to be terminated.
Re:SSH hacks – a little sanity for remote workers by yownie on Wednesday April 29, 2020 @10:02PM (#23026754)
or just sshuttle
Re:SSH hacks – a little sanity for remote workers by shawnz on Wednesday April 29, 2020 @10:12PM (#23026793)
Sshuttle solves a different problem. It uses SSH as a transport so it could not bypass a firewall that blocks outgoing SSH.