This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ssh [2017/05/19 20:38] – [SSH keys] deul | ssh [2017/05/19 20:42] – [Copy public key to server] deul | ||
---|---|---|---|
Line 22: | Line 22: | ||
--------- | --------- | ||
- | ====== SSH shell access | + | ====== SSH tunnels |
+ | For the Mac and Linux commandline ssh client, setting up a tunnel is usually a matter of using the option \\ | ||
+ | '' | ||
+ | for forwarding a Windows remote desktop. More detail can be found in the [[vnc|vnc ssh tuning pages]]. | ||
+ | |||
+ | See [[linux: | ||
+ | ====== SSH client software ====== | ||
+ | Linux and macOS come with a commandline client for ssh. | ||
+ | For Windows, the recommended client is [[linux: | ||
====== SSH keys ====== | ====== SSH keys ====== | ||
====Create a key pair==== | ====Create a key pair==== | ||
Line 57: | Line 66: | ||
id_dsa.pub | id_dsa.pub | ||
+ | This will place your keys in your home directory on the remote server. After that we will login on the remote server using ssh or telnet the conventional way... with a password. | ||
- | ====== SFTP and SCP file access ====== | + | When you are logged in you should create a .ssh directory, |
- | ====== SSH tunnels ====== | + | |
- | For the Mac and Linux commandline | + | |
- | '' | + | |
- | for forwarding a Windows remote desktop. More detail can be found in the [[vnc|vnc ssh tuning pages]]. | + | |
- | See [[linux: | + | Placing the key for version 2 works as follows: |
- | ====== | + | |
- | Linux and macOS come with a commandline client for ssh. | + | $ cd .ssh |
- | For Windows, the recommended client is [[linux: | + | $ touch authorized_keys2 |
+ | $ chmod 600 authorized_keys2 | ||
+ | $ cat ../ | ||
+ | $ rm ../ | ||
+ | |||
+ | From now on you can login from client | ||
+ | |||
+ | ====== |