I sometimes want to remote-desktop to an internal Windows server at work. The database server doesn't need to listen to its LAN at all, and can stay tightly firewalled My laptop's doesn't need to be trusted (the database never even sees its IP) So now, when something connects to my laptop's port 5432, like my own GUI, it actually goes to what on the the SSH server's networking side is localhost:5432Īs far as the dbserver is concerned, it's seeing a connection from its localhost. Say I have a database-exploring GUI on my laptop (pgadmin, dbeaver, etc.), and a database server in the corner of my room that has SSH open but is otherwise firewalled on that laptop I might do (e.g. here's some introduction via real uses I've had for it: Why that is useful is not immediately obvious, so. and from that other side there will be a new, non-secured (!) TCP connection, to the a host and port you also specified. It will be carried through that existing SSH connection to the other side.
0 Comments
Leave a Reply. |