16 m o d 5 = 1 16 \mod 5 = 1 1 6 m o d 5 = 1) you can understand Diffie-Hellman, as it’s only a few steps that could be done even on paper. If you’ve ever configured nginx and run into something called dhparam or ssl_dhparam, the dh in there stands for the Diffie-Hellman algorithm, which is an amazingly simple algorithm to exchange a secret key over an insecure communication channel, without any prior knowledge. There are three types of encryption used at different stages: Diffie-Hellman, RSA, and AES (or other algorithms depending on configuration).
You don’t need to understand it to use SSH tunnels in practice. If you just want to get to the practical bits, feel free to skip this section and jump straight to Local Port Forwarding. Backgroundīut first a tiny bit of background on how SSH works and why it’s secure.
We can use this channel to run commands on the remote server, expose a local port in a remote computer, expose a remote port on the local computer, or route traffic via a SOCKS proxy (more on this later). In its essence, port forwarding allows SSH to securely create an encrypted communication channel (a tunnel) between two computers on the network. In this post I hope to explain it in such a way that you’ll have no confusion about when to use SHH’s local, remote, or even dynamic port forwarding. SSH tunneling is an extremely useful feature of SSH that is very often googled, but less often understood enough to use without a reference. Dark theme SSH Tunnel - Local, Remote and Dynamic Port Forwarding
0 kommentar(er)
