3 ms·
This isn't really a configuration suggestion, more of an architecture suggestion: let's say you're like me and you have 5 VPSes. You want precisely one to have
by patio11 16y ago
This isn't really a configuration suggestion, more of an architecture suggestion: let's say you're like me and you have 5 VPSes. You want precisely one to have SSH exposed to the public Internet. Everybody else has SSH only listen on a private IP. (Your host can probably set those up for you. Slicehost does, for example.)
e.g.
ListenAddress 1.2.3.4 #This is not really your IP address.
You can go an extra step and drop all packets to the SSH port on the public interface in IPTables, if you want. It strikes me as being overkill but, hey, whatever.
If you need to log into any server, you do so by tunneling through your gatekeeper server. That fellow gets locked down tightly. All of your other servers are firewalled tight as drums, with the exception of public-facing HTTP servers who have 80 and 443 opened (and that is it).
- iuguy 16y agoThis is sound advice and I've seen this in quite a few small multi-server environments. The only thing I'd say is that once you get to 5 - 10 servers you might want to look at a VPN such as openVPN (http://www.openvpn.net/ http://www.openvpn.net/), at which point all your SSH services can run on their hidden networks. This makes a bigger difference as well if you have more than a few people accessing the boxes, and for purely remote-based businesses quite a few use this type of setup to host their 'internal' network tools like an intranet, file storage, internal wiki etc. If you have the cash and capability, I'd recommend an IPSEC VPN over OpenVPN (using something like a low-end Cisco ASA for example, but shop around - the point is to use dedicated hardware), but if you're starting out, OpenVPN is fine.