User Tools

Site Tools


login:sshsupport

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
login:sshsupport [2017/01/30 16:17] jaslogin:sshsupport [2020/02/10 10:33] (current) seela
Line 1: Line 1:
 ====== SSH Support ====== ====== SSH Support ======
  
-The preferred protocol for connecting to the Department from your home ISP or from another remote computer is SSH or Secure Shell. This protocol provides for the encryption of traffic in transit making it very difficult for a third party to snoop or listen in.+The best way to connect to Departmental systems from your computer is via SSH (Secure Shell) client The SSH protocol provides for the encryption of traffic in transit making it difficult for a third party to snoop or listen in.
  
-We operate ssh servers on our time-sharing servers. SSH clients must be used to access the EECS time-sharing servers from outside the Department+We operate SSH servers on all tech-supported Linux systems You can SSH from any tech-supported Linux system to any other tech-supported Linux system without a password.
  
-There are a number of available ssh clients for Unix, Windows and Macintosh.+===== External Access =====
  
-SSH From One Host To Another Without Entering A Password +In order to access Departmental systems externally (eg. from your home), you will first need to connect to a time sharing server.  From there, you can SSH to any other Departmental server 
-By default, you will be able to connect by SSH from any tech-supported departmental Unix machine to any other tech-supported departmental Unix machine without requiring a password.+
  
-If you would like to be able to connect to a non-tech-supported SSH server without entering a password, you will need to carry out a simple two-step process yourself.+**If you are an undergrad, you will use the time sharing server named "red.eecs.yorku.ca" If you are anyone else, you will use the time sharing server named "indigo.eecs.yorku.ca"**. 
 +  
 +===== SSH Clients ===== 
 + 
 +There are a number of available SSH clients for Unix, Windows and Mac machines.  Unix and Mac users typically use "ssh" from the command line like this: 
 + 
 +  % ssh indigo.eecs.yorku.ca -l <EECS USERNAME>  or 
 +  % ssh red.eecs.yorku.ca -l <EECS USERNAME> 
 + 
 +Windows 10 users can use the SSH command line tool as well.  However, most Windows users prefer a GUI.  For that, we recommend [[https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html|Putty]]. or [[https://mobaxterm.mobatek.net/download-home-edition.html|Mobaxterm]] 
 + 
 +===== SSH From One Host To Another Without Entering A Password ===== 
 + 
 +As mentioned above, you can SSH from any tech-supported Linux system to any other tech-supported Linux system without requiring a password. If you would like to be able to connect from a tech-supported Linux system to a non-tech-supported Linux system (eg. your personal Ubuntu workstation) without entering a password, you will need to carry out a few simple steps. 
 + 
 +First, run 'ssh-keygen' on one of the Departmental Unix hosts:
  
-First, run 'ssh-keygen' on one of the departmental Unix hosts: 
 <code> <code>
 % ssh-keygen -t rsa -N "" % ssh-keygen -t rsa -N ""
Line 18: Line 31:
 Enter file in which to save the key (/eecs/home/xxx/.ssh/id_rsa): Enter file in which to save the key (/eecs/home/xxx/.ssh/id_rsa):
  
-Hit "ENTER" to create the public key file.ssh/id_rsa.pub and the private key file .ssh/id_rsa.+Hit "ENTER".  The public key file (~/.ssh/id_rsa.puband the private key file (~/.ssh/id_rsa) will be created. 
 +</code>
  
-On the system that you would like to login to, you will now need to append the contents of the newly created .ssh/id_rsa.pub file to the .ssh/authorized_keys file. If the file does not exist, create it. Now, you will be able to ssh to your host from any departmental Unix system without requiring a password. +The public key file looks something like this: 
 + 
 +<code> 
 +ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCewDNfAREt/GlH1GL2an0W7Z+sigb3OrirSmjqJdK5PjlZNIB/E07z1CAzUu8AOEXAVt6+a84scyG3gojLUHZrXgMMP8uFfZEw/WkBsAY3gMlU+UqbZwngpTb1eAm4VkrF60hu02zDm1uRYdG4hI4wbyZhsYiYp/xatN1tcw3lKQB2XAojqBaLoSKpu5dfMDsKM42IlDrg530r2z+wdg2rc0jW8CQBGuE55a3Fr7IUvkblwtAG5ORhMlmjaOLO+oUEfm4gRlZ5X2/zN6IgE8yn93lOyuhuaoamyD0EY27oaauPiNhMKtiSI0maIBIk47gfK/nJtW2aRKiOvhx5BZ+x eecs@red
 </code> </code>
 +
 +Now, SSH to the destination system that you would like to be able to connect without entering a password (eg. your personal Ubuntu workstation).  The first time you access the system, you will still need to enter a password.
 +
 +Append the contents of the newly generated ~/.ssh/id_rsa.pub file to the authorized_keys file on the remote system (eg. ~/.ssh/authorized_keys on Linux systems). If the file does not exist, create it. 
 +
 +Now, you will be able to ssh from your tech-supported Linux host to the other machine without requiring a password.
  
login/sshsupport.1485811038.txt.gz · Last modified: 2017/01/30 16:17 by jas