I keep a machine which has sshd listening on the IMAPS port (993) for when I'm traveling. It's amazing how many free networks don't allow ssh, but with -J and sshd on port 993, that really doesn't matter.
Agreed. You can host both SSH and HTTPS on port 443. I know this used to be possible with HAProxy, but now Nginx can do it as well. This way you are hosting normal HTTPS traffic when a browser is used and SSH otherwise.
Now, if your company is actually blocking the SSH protocol, you’ll have to do something like tunneling SSH through SSL, which is also possible… but not as easier IIRC.
I agree. Something like what GitHub offers? https://docs.github.com/en/authentication/troubleshooting-ss...
Cockscrew might fit your usecase[1]
[1] - https://github.com/bryanpkc/corkscrew
Use that from home or a mobile phone connection?
You probably aren't supposed to update your personal website and stuff when you are working for your company anyway.
Stupid company!
I keep a machine which has sshd listening on the IMAPS port (993) for when I'm traveling. It's amazing how many free networks don't allow ssh, but with -J and sshd on port 993, that really doesn't matter.
A NGFW, frequently used in the enterprise environments will block it. They are checking the package signatures, not only the YCP ports.
I have heard that SSH could be tunneled over DNS UDP packets.
This looks like a decent article, will read later.
https://medium.com/@rogergalo/learn-how-easy-is-to-bypass-fi...
Not sure if it has to go that far. Probably it's just blocking port 22.
Agreed. You can host both SSH and HTTPS on port 443. I know this used to be possible with HAProxy, but now Nginx can do it as well. This way you are hosting normal HTTPS traffic when a browser is used and SSH otherwise.
Now, if your company is actually blocking the SSH protocol, you’ll have to do something like tunneling SSH through SSL, which is also possible… but not as easier IIRC.