[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Encrypt data between socket client and server
[Thread Prev] | [Thread Next]
- Subject: Re: Encrypt data between socket client and server
- From: Lee <t.lee.davidson@xxxxxxxxx>
- Date: Thu, 5 Mar 2026 13:21:26 -0500
- To: user@xxxxxxxxxxxxxxxxxxxxxx
On 3/5/26 7:26 AM, gbWilly wrote:
I like the SSH tunnel idea.So, if a socket daemon would be listening at port 2000 in your example and my socket client is operating a port 1000 in your example, just first creating the tunnel would make socket client and server communicate over the tunnel?Do I get that right that, once this tunnel is made all communication between those 2 ports will be over that tunnel.
Wow, SSH tunneling appears to be simpler than I originally thought. I believe the answer to both your questions is, Yes.As I understand it now, the command "ssh -f <user>@machine2 -L 1000:127.0.0.1:2000 -N" essentially means, forward local port 1000 through the remote SSH server to remote port 2000. Responses from remote port 2000 should follow the reverse path and be encrypted as well.
Here is a useful article I found on the topic: https://linuxize.com/post/how-to-setup-ssh-tunneling/#local-port-forwarding -- Lee --- Gambas User List Netiquette [https://gambaswiki.org/wiki/doc/netiquette] ---- --- Gambas User List Archive [https://lists.gambas-basic.org/archive/user] ----
| Encrypt data between socket client and server | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
| Re: Encrypt data between socket client and server | Lee <t.lee.davidson@xxxxxxxxx> |
| Re: Encrypt data between socket client and server | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
| Re: Encrypt data between socket client and server | Lee <t.lee.davidson@xxxxxxxxx> |
| Re: Encrypt data between socket client and server | Olivier Cruilles <olivier.cruilles@xxxxxxxx> |
| Re: Encrypt data between socket client and server | gbWilly <gbWilly@xxxxxxxxxxxxxx> |