Differences

This shows you the differences between two versions of the page.

--- ssh-remote [2007/07/14 10:58] – damir
+++ ssh-remote [2007/08/01 18:00] (current) – damir
@@ Line 1: / Line 1: @@
 ====== HowTo connect to servers using SSH ======
-To connect to server, local or remote, you can use the **ssh** client program. When you start a connection to the server using this program, the two machine involved, encrypt all the network traffic generated, so nobody can spy on your connection and see what you are doing. This kind of connection is the only one available if you want to use terminal session to connect to our servers, no matter if the connection is made locally or from a remote workstation.
+To connect to server, local or remote, you can use the **ssh** client program. When you start a connection to the server using this program, the two machine involved, encrypt all the network traffic generated, so nobody can spy on your connection and see what you are doing. __This kind of connection is the only one available if you want to use terminal session to connect to our servers__, no matter if the connection is made locally or from a remote workstation.
@@ Line 18: / Line 21: @@
 If you are using the session of another user, to access the remote server, use the **-l <username>** parameter in order to indicate the username you want use on the remote machine.\\
 \\
-Windows users can use [[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html|putty]], a ssh client with graphical interface, or install the CygWin.
+Windows users can use [[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html|putty]], a ssh client with graphical interface, or install [[http://www.cygwin.com/|CygWin]], the Linux-like environment for Windows.
 </note>
@@ Line 33: / Line 36: @@
 If you use this trick to see the graphical interface of a machine connected on the other side of the planet, check the bandwidth you can use. X connection require a lot of bandwidth.
 </note>
 ===== How Access more than one Server =====
-In a perfect world, Firewalls doesn't exist, but here on earth, Firewalls are absolutely necessary. Firewalls have just one mission: //block everything suspicious or dangerous that is transmitted on the network//. To do this the Firewalls limits the possibilities of connection from remote networks, no matter if the user connecting is good or bad. Of course this means disadvantages for the allowed user that can't access directly the servers of the protected network, but must pass from a **gateway**.
+In a perfect world, Firewalls doesn't exist, but here on earth, Firewalls are absolutely necessary. Firewalls have just one mission: __//block everything suspicious or dangerous that is transmitted on the network//__. To do this the Firewalls limits the possibilities of connection from remote networks, no matter if the user connecting is good or bad. Of course this means disadvantages for the allowed user that can't access directly the servers of the protected network, but must pass from a **gateway**.
 The simple solution is to connect to the gateway and then, from the gateway, open a ssh connection to the remote server. This can be annoying and difficult if you have to  connect to different remote server at the same time.\\