meta data for this page
  •  

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
general:computerenvironment:ssh [2021/10/14 20:09] – ingogeneral:computerenvironment:ssh [2024/06/18 09:26] (current) – ingo
Line 1: Line 1:
 ====== Remote login via SSH ====== ====== Remote login via SSH ======
-[[wp>ssh]], the secure shell, is a way to establish a connection between two computers. In fact, you use it to login on a remote computer system, e.g. when you connect to our local computer system from home. Typically, you will have to provide a user name and a password to establish the connection. In our case, the authentication is done via a certificate that we provide you with at the beginning of the course((We do this only when it will be an online course)).+[[wp>ssh]], the secure shell, is a way to establish a connection between two computers. In fact, you use it to login on a remote computer system, e.g. when you connect to our local computer system from home. Typically, you will have to provide a user name and a password to establish the connection. In our case, the authentication is done via a certificate that we provide you with at the beginning of the course((We do this only when it will be an online course)). We differentiate between two scenarios: 
 +  * ssh from within our network 
 +  * ssh from outside of our network 
 +===== ssh connections within the network ===== 
 +<wrap question></wrap>You do this if you want to access a computer that 
 +   * has more computer power 
 +   * has more RAM 
 +   * is less busy 
 +than the one you are sitting one.
  
-===== Things you need to have =====+:!: You need 
 +   * your username 
 +   * your password 
 +   * the name or the IP address of the computer you want to connect to 
 +<hidden Example> 
 +   * username: ingo 
 +   * password: 1234secret 
 +   * pool20 
 +<code> 
 +ssh -u ingo pool20 
 +</code> 
 +You will then be prompted to provide the password for the user //ingo//. <wrap important>The cursor will not move when you type your password, so don't worry.</wrap> If the authentication was successful, you will be granted access to the remote computer. :!: If you do an ssh within the network, you can omit the option ''-u ingo''. This information is only required if your user name on the computer you establish the information from is different from your user name on the remote computer 
 +</hidden> 
 +===== ssh connection from outside of the network ===== 
 +For security reason, you can access our computers via ssh from outside of our network only when you have a VPN((virtual private network)) connection established. This requires a ovpn certificate provided by us. Please follow the steps below to set up the VPN.
 <WRAP info> <WRAP info>
-  - an email with a zip archive containing the openssh certificate, a key and the password +we have provided you with a OVPN certificate, that allows you to connect your local computer with our private network. 
-  - your user name in our system. The file name of the zip archive (without the ending .zip) should be your username((we use username and account name synonymously in this WIKI)) in our system. Typically, this will follow one of the three naming schemes<WRAP> +  - Download the certificate to your local computer 
-     - ecoevo01, ecoevo02, etc  +  - gunzip the certificate<WRAP> 
-     - pbioc01, pbioc02, etc +<code> 
-     - mbwt01, mbwt02, etc +gunzip *.ovpn.gz 
-</WRAP>Do you get the idea? <wrap tip></wrap>It can happen that the zip file starts with something like 'ssh-' before your user name, then please ignore this in the steps further below.<WRAP important> +</code></WRAP> 
-If you are unsure that you got the right username, ask the tutors. Using the wrong name will give you quite some headaches further down... +  - Install an open VPN client on your local machine 
-</WRAP>   +    - Windows users: install [[https://openvpn.net/community-downloads/|OpenVPN connect client]] 
-  - the unpacked zip archive containing the following files +    - Mac users 
-    - openssh (the certificate) +      - install [[https://tunnelblick.net|Tunnelblick]] 
-    - openssh.pub (the public key((you don't have to bother with this file)) +      - on an iPad, you can install the OpenVPN Connect App 
-    - password.txt (a text file with your password for the ssh connection((this is not your password for the login within our system))+  - load the certificate 
 +  - activate the VPN connection 
 +    - for this, you will need the username and the password provided by us((If you are unsure that you got the right username, ask the tutors. Using the wrong name will give you quite some headaches further down.))
   - an [[general:computerenvironment:openterminal|open terminal/shell]]   - an [[general:computerenvironment:openterminal|open terminal/shell]]
   - The [[wp>IP_address|IP address]] of our gateway: **141.2.46.150**   - The [[wp>IP_address|IP address]] of our gateway: **141.2.46.150**
 </WRAP> </WRAP>
 +
 +====How the login via ssh works ====
 +If you have all the information specified above at hand, proceed to the next steps
 +   * SSH from a [[general:computerenvironment:ssh_windows|Windows]] machine
 +   * SSH from Mac %%OS%% or Linux: Take a look at the [[https://www.youtube.com/watch?v=DawSa8S1GUM|following clip]]
 +
 +=== Example ===
 +
 +Type the following example command in the terminal window, where openssh22 is your certificate, and pbioc01 is your account. You will be prompted to introduce your password.
 +<code>
 +# To connect to the server
 +ssh -i pbioc_course/openssh22 pbioc01@141.2.46.150
 +
 +# Select a working station
 +ssh pool01
 +
 +# Copy files from your personal computer to our computer system.
 +# Syntax: scp <ssh key> <target file> <where to paste it>
 +scp -i pbioc_course/openssh22 file.fasta pbioc01@141.2.46.150:/home/pbioc06
 +scp -i pbioc_course/openssh22 pbioc01@141.2.46.150:/home/pbioc06/file.png ~/Desktop 
 +</code>
 +If you encounter the message "WARNING: UNPROTECTED PRIVATE KEY FILE". You will need to change the permissions in your ssh certificate. 
 +<code>
 +chmod 400 openssh22
 +</code>
 +
 +
 <WRAP tabs> <WRAP tabs>
    * [[general:computerenvironment]]    * [[general:computerenvironment]]
 </WRAP> </WRAP>