User Tools

Site Tools



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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
ssh [2017/01/27 09:58]
ssh [2019/05/06 09:16]
jansen remove references to authorized_keys2, add section for local use with shared home directory
Line 5: Line 5:
 If you do not have a personal machine you can use the ''​''​ virtual machine to log into our systems and continue from there with an ssh to any of the science servers or cluster machines. If you do not have a personal machine you can use the ''​''​ virtual machine to log into our systems and continue from there with an ssh to any of the science servers or cluster machines.
 +=== Special access ===
 +Some places we visit (e.g. China or Iran) or some hotels abroad limit the internet access to web browsing only. Because you want more in such cases the ssh server of the Sterrewacht now also serves the ssh protocol on web ports 80 and 443. So you can now get access to the Sterrewacht computer systems from those limiting environments using
 +  ssh -p 80 -l <your STRW accountname>​
 +With this type of connectivity you can add the tunnelling options (as indicated below) to gain connectivity to a windows remote desktop or your Linux VNC environment. ​
 ===== Instituut Lorentz ===== ===== Instituut Lorentz =====
Line 15: Line 22:
 --------- ---------
-====== SSH shell access ====== 
-====== SSH keys ====== 
-====== SFTP and SCP file access ====== 
 ====== SSH tunnels ====== ====== SSH tunnels ======
 +For the Mac and Linux commandline ssh client, setting up a tunnel is usually a matter of using the option \\
 +''​%%-L local_port:​remote_machine:​remote_port%%'',​ e.g. ''​%%-L 3389:​windows machine:​3389%%''​ \\
 +for forwarding a Windows remote desktop. More detail can be found in the [[vnc|vnc ssh tuning pages]].
 +See [[linux:​putty]] for instructions about setting up a tunnel with ''​%%putty%%''​ (Windows, linux ssh client).
 ====== SSH client software ====== ====== SSH client software ======
 Linux and macOS come with a commandline client for ssh. Linux and macOS come with a commandline client for ssh.
 For Windows, the recommended client is [[linux:​putty]] For Windows, the recommended client is [[linux:​putty]]
 +====== SSH keys ======
 +====Create a key pair====
 +To create the most simple key, with the default encryption, open up a console, and enter the following command:
 +  $ ssh-keygen -t dsa
 +  Generating public/​private dsa key pair.
 +  Enter file in which to save the key (/​home/​xxxx/​.ssh/​id_dsa): ​
 +  Enter passphrase (empty for no passphrase): ​
 +  Enter same passphrase again: ​
 +  Your identification has been saved in /​home/​xxxx/​.ssh/​id_dsa.
 +  Your public key has been saved in /​home/​xxxx/​.ssh/​
 +  The key fingerprint is:
 +  7b:​ab:​75:​32:​9e:​b6:​6c:​4b:​29:​dc:​2a:​2b:​8c:​2f:​4e:​37 xxxx@yyyy
 +When asked for a "​passphrase",​ we won't enter one. Just press enter twice.
 +The ssh-keygen program will now generate both your public and your private key. For the sake of this first simple tutorial I will call these files by their default names "​identity"​ and the public key "​"​.
 +Your keys are stored in the .ssh/ directory in your home directory, but you can store them where ever you'd like.
 +The file identity contains your private key. YOU SHOULD GUARD THIS KEY WITH YOUR LIFE! This key is used to gain access on systems which have your private key listed in their authorized keys file. I cannot stress this enough, dont have your keys drifting around. Also, make sure your private key always is chmod 600, so other users on the system won't have access to it.
 +The file contains your public key, which can be added to other system'​s authorized keys files.
 +====Simplified version in case of a shared home disk====
 +This is how you authorize the key for use within a local network with shared home disk. See below for the general case of accessing a remote system.
 +Simply add the public part of the key to your .ssh/​authorized_keys file, and make sure that that file is not accessible for others:
 +  cat ~/​.ssh/​ >> ~/​.ssh/​authorized_keys
 +  chmod 600 ~/​.ssh/​authorized_keys
 +====Copy public key to server====
 +To be able to log in to remote systems using your pair of keys, you will first have to add your public key on the remote server to the authorized_keys (for version 1) file, and the authorized_keys2 (for version2) file in the .ssh/ directory in your home directory on the remote machine.
 +In our example we will assume you don't have any keys in the authorized_keys files on the remote server. (Hint: If you do not have a remote shell, you can always use your own useraccount on your local machine as a remote shell (ssh localhost))
 +First we will upload the public keys to the remote server:
 +  $ cd .ssh/
 +  $ scp xxxx@zzzz:​./​
 + ​   100% |*****************************************************| ​  ​526 ​      00:00
 +This will place your keys in your home directory on the remote server. After that we will login on the remote server using ssh the conventional way... with a password.
 +When you are logged in you should create a .ssh directory, and inside the .ssh/ directory create an authorized_keys file and add the keys to the file. Make sure the files are not readable for other users/​groups. chmod 600 authorized_keys does the trick.
 +Placing the key works as follows:
 +  $ cd .ssh
 +  $ touch authorized_keys
 +  $ chmod 600 authorized_keys
 +  $ cat ../​ >> authorized_keys
 +  $ rm ../​
 +From now on you can login from client yyyy to server zzzz without having to specify a password.
ssh.txt ยท Last modified: 2020/10/22 12:12 by jansen