ssh - Revision history

Woozle: /* Links */

2020-02-16T20:18:40Z

Links

← Older revision		Revision as of 20:18, 16 February 2020
Line 17:		Line 17:
	* [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/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.		* [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]

Woozle at 19:17, 23 October 2019

2019-10-23T19:17:21Z

← Older revision		Revision as of 19:17, 23 October 2019
Line 1:		Line 1:
	==About==		==About==
	{{seed}}		{{seed}}
			===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==		==Related==
	* [[keyed login]]: enable logging in from a specific remote client with no password (useful for scripts)		* [[keyed login]]: enable logging in from a specific remote client with no password (useful for scripts)
	* [[ssh-keygen]]		* [[ssh-add]]: manages keys for the [[ssh-agent]]
			* [[ssh-agent]]: background process used by [[ssh]]
			* [[ssh-keygen]]: creates new keys
	* [[sshfs]]: a filesystem for mounting remote folders via ssh		* [[sshfs]]: a filesystem for mounting remote folders via ssh
	==How-to==		==How-to==
Line 10:		Line 14:
	===Reference===		===Reference===
	* {{wikipedia\|Secure Shell}}		* {{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.

Woozle: tidying & slight updating

2019-10-23T18:47:47Z

tidying & slight updating

← Older revision		Revision as of 18:47, 23 October 2019
Line 1:		Line 1:
			==About==
	{{seed}}		{{seed}}
	==~~Notes~~==		==Related==
	To enable logging in from a specific remote client with no password (~~most often used~~ for scripts)~~, see~~ [[~~keyed login~~]].		* [[keyed login]]: enable logging in from a specific remote client with no password (useful for scripts)
			* [[ssh-keygen]]
			* [[sshfs]]: a filesystem for mounting remote folders via ssh
			==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>.		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>.
			==Links==
			===Reference===
			* {{wikipedia\|Secure Shell}}

Woozle: break a dead connection

2018-01-04T14:50:39Z

break a dead connection

← Older revision		Revision as of 14:50, 4 January 2018
Line 2:		Line 2:
	==Notes==		==Notes==
	To enable logging in from a specific remote client with no password (most often used for scripts), see [[keyed login]].		To enable logging in from a specific remote client with no password (most often used for scripts), see [[keyed login]].

			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>.

Woozle at 13:30, 6 April 2017

2017-04-06T13:30:16Z

@@ Line 1: / Line 1: @@
 {{seed}}
 ==Notes==
-To enable logging in from a specific remote client with no password (typically so scripts can connect with ssh or [[rsync]]):
+To enable logging in from a specific remote client with no password (most often used for scripts), see [[keyed login]].

Woozle: corrections & a command

2014-09-23T14:40:15Z

corrections & a command

← Older revision		Revision as of 14:40, 23 September 2014
Line 3:		Line 3:
	To enable logging in from a specific remote client with no password (typically so scripts can connect with ssh or [[rsync]]):		To enable logging in from a specific remote client with no password (typically so scripts can connect with ssh or [[rsync]]):
	* Generate a public/private key pair on the client using [[ssh-keygen]]		* Generate a public/private key pair on the client using [[ssh-keygen]]
	* ~~Copy~~ the public key file (~/.ssh/id_rsa.pub) from the client to ~/.ssh/authorized_keys		* Add the public key file (~/.ssh/id_rsa.pub) from the client to ~/.ssh/authorized_keys on the host.
	** If the latter file doesn't already exist, then it can just be a direct copy of id_rsa.pub.		** If the latter file doesn't already exist, then it can just be a direct copy of id_rsa.pub.
	** If the latter file ''does'' already exist, then id_rsa.pub can just be appended to authorized_keys.		** If the latter file ''does'' already exist, then id_rsa.pub can just be appended to authorized_keys.
			** The following command should work for either case:
			*** <bash>cat .ssh/id_rsa.pub \| ssh user@host 'cat >> .ssh/authorized_keys'</bash>
	* 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.		* 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.
	* 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.		* 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.

Woozle: clarifications and a link

2013-11-17T14:16:44Z

clarifications and a link

← Older revision		Revision as of 14:16, 17 November 2013
Line 5:		Line 5:
	* Copy the public key file (~/.ssh/id_rsa.pub) from the client to ~/.ssh/authorized_keys		* Copy the public key file (~/.ssh/id_rsa.pub) from the client to ~/.ssh/authorized_keys
	** If the latter file doesn't already exist, then it can just be a direct copy of id_rsa.pub.		** If the latter file doesn't already exist, then it can just be a direct copy of id_rsa.pub.
	** If the latter file ''does'' already exist, then id_rsa.pub can ~~presumably~~ just be appended to authorized_keys ~~although I have not yet verified this~~.		** If the latter file ''does'' already exist, then id_rsa.pub can just be appended to authorized_keys.
	* 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.		* 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.
	* 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.		* 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.
			* 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.

			Specific commands for doing this may be found [http://linuxproblem.org/art_9.html here].

Woozle: Created page with "{{seed}} ==Notes== To enable logging in from a specific remote client with no password (typically so scripts can connect with ssh or rsync): * Generate a public/private ke..."

2013-05-28T18:22:12Z

Created page with "{{seed}} ==Notes== To enable logging in from a specific remote client with no password (typically so scripts can connect with ssh or rsync): * Generate a public/private ke..."

New page

{{seed}}
==Notes==
To enable logging in from a specific remote client with no password (typically so scripts can connect with ssh or [[rsync]]):
* Generate a public/private key pair on the client using [[ssh-keygen]]
* Copy the public key file (~/.ssh/id_rsa.pub) from the client to ~/.ssh/authorized_keys
** If the latter file doesn't already exist, then it can just be a direct copy of id_rsa.pub.
** If the latter file ''does'' already exist, then id_rsa.pub can presumably just be appended to authorized_keys although I have not yet verified this.
* 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.
* 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.