That is just an abstract definition. I use SSH to do much more. Here are just some simple commands that I used to run for such a different reasons:
Whenever I need to pass stupid filtering of stupid government
ssh -D 8888 firstname.lastname@example.org
"100.101.102.103" is just the host that you want to connect it. I assumed that 100.101.102.103 is a SSH enabled machine.
This command simply forwards the remote machine's HTTP port to my local machine. So I just need to use a socks4 proxy like this : 127.0.0.1:8888.
So whatever you do using your browser will forward to the remote machine. The channel between your local machine and the remote one is pretty secured. However, the remote machine should be trusted.
Whenever I need to connect a remote MS-SQLServer on a windows machine using my Linux machine
Assume a service such as SQLServer which runs on a machine that is hosted in a remote LAN with [192.168.0.100] IP address. Assume you just can connect to another machine that is hosted in the same LAN using:
Assume again the MS-SQLServer uses the port number 1433.
I need to connect to the ssh server machine using ssh email@example.com moreover I need to forward 192.168.0.100:1433 to my local machine. This is the simple solution:
ssh -L 1433:192.168.0.100:1433 firstname.lastname@example.org -N
The pattern is "ssh -L myPort:host:hostPort". -N is useful for just forwarding ports and nothing else.
The connections could be same as below map:
my machine ssh server MS-SQLServer
127.0.0.1 <===> 100.101.102.103 <===> 192.168.0.100
-Install OpenSSH if you need to provide SSH over Windows servers.
-To access ports under 1024 you should have root privilege.