3 ms·
> Each port is also limited to a single machine, so you'd have to choose a different port for a different machine. I would probably set up one gateway machine,
by marginalia_nu 5y ago
> Each port is also limited to a single machine, so you'd have to choose a different port for a different machine.
I would probably set up one gateway machine, and then from that machine log into other machines on the network; instead of exposing them all to the Internet. SSH allows you to chain logins thus:
ssh -A -t user@public-gateway ssh -A -t user2@server-behind-dmz
It's a lot less work to lock down one machine really tight enough to expose them to the public Internet than to do it on the entire network.
- jgtrosh 5y agoUse -J or ProxyJump in .SSH/config for a modern equivalent
- lxgr 5y agoYes, please only use this! The big advantage of this (over ssh user@host1 ssh user@host2) is that the jump host only sees the encrypted inner connection – it doesn't get access to the client's SSH agent/keychain, nor to the target host (host2) or data transmitted over the connection.
- marginalia_nu 5y agoI guess my bash aliases are a bit oldfashioned :P
- amiller2571 5y agoThat's how we do it where I work. We have a bastion server we SSH into to access other systems in the network. Pretty easy to setup SSH to use it to hop through with just one command. https://www.redhat.com/sysadmin/ssh-proxy-bastion-proxyjump https://www.redhat.com/sysadmin/ssh-proxy-bastion-proxyjump
- trinovantes 5y agoI use this alias in my .ssh/config to connect through a gateway machine: Host myserver User user ProxyCommand ssh -q public-server nc -q0 private-server 22 I can't remember what these flags actually do but they seem to get the job done
- taftster 5y agoProxyJump is slightly preferred in modern SSH. Does what you're doing, but with simpler syntax. Take a look.
- trinovantes 5y agoThanks, I see that it's a fairly recent addition to OpenSSH I wrote that alias about a decade ago when it wasn't available for me yet
- taftster 5y agoYeah, it's a new parameter, based on exactly this common use case.
- neurostimulant 5y agoUnfortunately it doesn't work if you're behind a NAT due to shitty ISP, like me. I use AutoSSH instead to expose my local machine's ssh port on a high port in the gateway machine: `autossh -M 0 -o "ServerAliveInterval 30" -o "ServerAliveCountMax 3" -v -N -R 22222:localhost:22 user@my-vps-domain` ServerAliveInterval 30 is important because my ISP often drop idle connections, often not even 1 minute idle. Can probably tweak it to listen to a localhost only port instead of exposing them to internet.