Difference between revisions of "ssh"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(clarifications and a link)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
==About==
 
{{seed}}
 
{{seed}}
==Notes==
+
===Processes===
To enable logging in from a specific remote client with no password (typically so scripts can connect with ssh or [[rsync]]):
+
New keys are generated with [[ssh-keygen]]. [[ssh]] interacts with keys via [[ssh-agent]], which needs to have keys registered with it using [[ssh-add]] before it can use them.
* Generate a public/private key pair on the client using [[ssh-keygen]]
+
==Related==
* Copy the public key file (~/.ssh/id_rsa.pub) from the client to ~/.ssh/authorized_keys
+
* [[keyed login]]: enable logging in from a specific remote client with no password (useful for scripts)
** If the latter file doesn't already exist, then it can just be a direct copy of id_rsa.pub.
+
* [[ssh-add]]: manages keys for the [[ssh-agent]]
** If the latter file ''does'' already exist, then id_rsa.pub can just be appended to authorized_keys.
+
* [[ssh-agent]]: background process used by [[ssh]]
* It may be necessary to manually log on once to the client from the host (using the same usernames as above) in order to add the client to the host's known_hosts file; I'm not sure about this part. Need to test.
+
* [[ssh-keygen]]: creates new keys
* Manually log on from the client to the host to make sure that the host is added to the client's known_hosts file, otherwise the verification prompt may interrupt any processes trying to log on automatically.
+
* [[sshfs]]: a filesystem for mounting remote folders via ssh
* If you disable logins now (e.g. via [[Webmin]]'s "No login allowed" option), you will still be able to log in from a client with an authorized key.
+
==How-to==
 
+
To break a dead connection and get back to a local prompt, try <code>[ENTER]~.</code> or (in MATE Terminal, at least) <code>Terminal->Reset</code>.
Specific commands for doing this may be found [http://linuxproblem.org/art_9.html here].
+
==Links==
 +
===Reference===
 +
* {{wikipedia|Secure Shell}}
 +
===How-to===
 +
* [https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent Generating a new SSH key and adding it to the ssh-agent] (see also [[ssh-keygen]], [[ssh-agent]])
 +
* [https://help.github.com/en/github/authenticating-to-github/checking-for-existing-ssh-keys Checking for existing SSH keys]: note that a key may ''exist'' without [[ssh]] being able to use it; keys must be registered through [[ssh-add]] so that they can be used.
 +
* '''2015-10-05''' [https://bjornjohansen.no/ssh-timeout SSH timeout prevention – keep SSH sessions alive]

Latest revision as of 20:18, 16 February 2020

About

This page is a seed article. You can help HTYP water it: make a request to expand a given page and/or donate to help give us more writing-hours!

Processes

New keys are generated with ssh-keygen. ssh interacts with keys via ssh-agent, which needs to have keys registered with it using ssh-add before it can use them.

Related

How-to

To break a dead connection and get back to a local prompt, try [ENTER]~. or (in MATE Terminal, at least) Terminal->Reset.

Links

Reference

How-to