If I understand correctly, SSH tunneling works as follows:
- Machine B is running the SSH daemon (process
- Machine A opens an ssh client (process
- Machine A connects its ssh client to machine B's server (say on port 22). In other words, process
aon machine A is communicating with process
bon machine B.
- A tunnel is opened, say by running
-L 4444:localhost:5555on machine A.
- Any traffic to
localhost:4444on machine A is intercepted and sent to process
a, who sends a special message over the connection on port 22
breceives the special message, and redirects to
localhost:5555on machine B.
Is there a replacement for processes
b that performs this tunneling trick but that isn't SSH? In other words, it doesn't have to perform encryption, and importantly, does not require the user on machine A to log into machine b?