How to use ssh keys - Revision history

Pashdown: source -> syntaxhighlight

2025-03-26T01:07:02Z

source -> syntaxhighlight

← Older revision		Revision as of 19:07, 25 March 2025
Line 27:		Line 27:

	* To create an SSH key that uses ED25519 you would type the following ...		* To create an SSH key that uses ED25519 you would type the following ...
	<~~source~~ lang=bash>		<syntaxhighlight lang=bash>
	ssh-keygen -t ed25519		ssh-keygen -t ed25519
	</~~source~~>		</syntaxhighlight>

	* You will be prompted for some information		* You will be prompted for some information
Line 41:		Line 41:
	* Entering in a passphrase will give you more security - however if your overall goal is to not have to enter a password everytime you ssh to a server then you do not need to enter a passphrase.		* Entering in a passphrase will give you more security - however if your overall goal is to not have to enter a password everytime you ssh to a server then you do not need to enter a passphrase.
	* The entire process will look something like this		* The entire process will look something like this
	<~~source~~ lang=bash>		<syntaxhighlight lang=bash>
	ssh-keygen -t ed25519		ssh-keygen -t ed25519
	</~~source~~>		</syntaxhighlight>
	<code><pre>		<code><pre>
	Generating public/private ed25519 key pair.		Generating public/private ed25519 key pair.
Line 72:		Line 72:

	* Next you will want to copy your public keys to the remote server - you can use a protocol called ssh-copy-id		* Next you will want to copy your public keys to the remote server - you can use a protocol called ssh-copy-id
	<~~source~~ lang=bash>		<syntaxhighlight lang=bash>
	ssh-copy-id user@machine		ssh-copy-id user@machine
	</~~source~~>		</syntaxhighlight>

	'''NOTE''' if the file authorized_keys does not exist you will have to create it.		'''NOTE''' if the file authorized_keys does not exist you will have to create it.

Pashdown: server -> linux, Mac OS X -> macOS

2025-03-26T01:02:58Z

server -> linux, Mac OS X -> macOS

← Older revision		Revision as of 19:02, 25 March 2025
Line 52:		Line 52:
	Your public key has been saved in /user/.ssh/id_ed25519.pub.		Your public key has been saved in /user/.ssh/id_ed25519.pub.
	The key fingerprint is:		The key fingerprint is:
	SHA256:/etv442E/ncLYkKZ8h2Hd0SZV3Cn+HHgyN6kECqYcPs user@~~server~~		SHA256:/etv442E/ncLYkKZ8h2Hd0SZV3Cn+HHgyN6kECqYcPs user@linux
	The key's randomart image is:		The key's randomart image is:
	+--[ED25519 256]--+		+--[ED25519 256]--+
Line 107:		Line 107:

	===Mac===		===Mac===
	* Very similar to Linux - Just make sure you are using ~~Mac OS X~~		* Very similar to Linux - Just make sure you are using macOS
	* Open a Terminal window found in Go > Applications > Utilities > Terminal		* Open a Terminal window found in Go > Applications > Utilities > Terminal
	<code><pre>		<code><pre>
Line 143:		Line 143:
	* cd .ssh		* cd .ssh
	* vim authorized_keys		* vim authorized_keys
	* Paste the contents from your ~~mac~~ id_ed25519.pub into this file		* Paste the contents from your Mac id_ed25519.pub into this file

Pashdown: update from rsa to ed25519

2025-03-26T01:01:12Z

update from rsa to ed25519

Show changes

Pashdown: Undo revision 11827 by Pashdown (talk)

2025-03-25T20:19:04Z

Undo revision 11827 by Pashdown (talk)

← Older revision		Revision as of 14:19, 25 March 2025
Line 8:		Line 8:
	** Your password is never sent over the network		** Your password is never sent over the network
	** You can connect to multiple servers without having to remember to enter your password for each attempt.		** You can connect to multiple servers without having to remember to enter your password for each attempt.
	** test
	* Below we will take you though some of the basic step of creating SSH keys.		* Below we will take you though some of the basic step of creating SSH keys.

Pashdown: test

2025-03-25T20:18:50Z

test

← Older revision		Revision as of 14:18, 25 March 2025
Line 8:		Line 8:
	** Your password is never sent over the network		** Your password is never sent over the network
	** You can connect to multiple servers without having to remember to enter your password for each attempt.		** You can connect to multiple servers without having to remember to enter your password for each attempt.
			** test
	* Below we will take you though some of the basic step of creating SSH keys.		* Below we will take you though some of the basic step of creating SSH keys.

Pashdown: /* Linux */

2015-04-30T15:33:38Z

Linux

← Older revision		Revision as of 09:33, 30 April 2015
Line 42:		Line 42:
	<source lang=bash>		<source lang=bash>
	ssh-keygen -t rsa		ssh-keygen -t rsa
			</source>
			<code><pre>
	Generating public/private rsa key pair.		Generating public/private rsa key pair.
	Enter file in which to save thr key (/user/.ssh/id_rsa):		Enter file in which to save thr key (/user/.ssh/id_rsa):
Line 62:		Line 64:
	\| .. . \|		\| .. . \|
	+-----------------+		+-----------------+
	</~~source~~>		</pre></code>

	* You now have 2 files stored in ~/.ssh		* You now have 2 files stored in ~/.ssh

Pashdown: /* Linux */

2015-04-30T15:32:59Z

Linux

← Older revision		Revision as of 09:32, 30 April 2015
Line 43:		Line 43:
	ssh-keygen -t rsa		ssh-keygen -t rsa
	Generating public/private rsa key pair.		Generating public/private rsa key pair.
	Enter file in which to save ~~teh~~ key (/user/.ssh/id_rsa):		Enter file in which to save thr key (/user/.ssh/id_rsa):
	Enter passphrase (empty for no passphrase):		Enter passphrase (empty for no passphrase):
	Enter same passphrase again:		Enter same passphrase again:
Line 50:		Line 50:
	The key fingerprint is:		The key fingerprint is:
	e7:38:47:65:25:71:ff:1c:ee:e4:a8:37:31:0d:58:80 user@server		e7:38:47:65:25:71:ff:1c:ee:e4:a8:37:31:0d:58:80 user@server
	The ~~key's~~ randomart image is:		The keys randomart image is:
	+--[ RSA 2048]----+		+--[ RSA 2048]----+
	\| ..+.o \|		\| ..+.o \|

Pashdown: change "code" to "source"

2015-04-30T15:30:42Z

change "code" to "source"

← Older revision		Revision as of 09:30, 30 April 2015
Line 26:		Line 26:

	* To create an SSH key that uses RSA you would type the following ...		* To create an SSH key that uses RSA you would type the following ...
	<~~code~~>		<source lang=bash>
	$ssh-keygen -t rsa		ssh-keygen -t rsa
	</~~code~~>		</source>

	* You will be prompted for some information		* You will be prompted for some information
Line 40:		Line 40:
	* Entering in a passphrase will give you more security - however if your overall goal is to not have to enter a password everytime you ssh to a server then you do not need to enter a passphrase.		* Entering in a passphrase will give you more security - however if your overall goal is to not have to enter a password everytime you ssh to a server then you do not need to enter a passphrase.
	* The entire process will look something like this		* The entire process will look something like this
	<~~code><pre~~>		<source lang=bash>
	ssh-keygen -t rsa		ssh-keygen -t rsa
	Generating public/private rsa key pair.		Generating public/private rsa key pair.
Line 62:		Line 62:
	\| .. . \|		\| .. . \|
	+-----------------+		+-----------------+
	</~~pre></code~~>		</source>

	* You now have 2 files stored in ~/.ssh		* You now have 2 files stored in ~/.ssh
Line 69:		Line 69:

	* Next you will want to copy your public keys to the remote server - you can use a protocol called ssh-copy-id		* Next you will want to copy your public keys to the remote server - you can use a protocol called ssh-copy-id
	<~~code~~>		<source lang=bash>
	ssh-copy-id user@machine		ssh-copy-id user@machine
	</~~code~~>		</source>

	'''NOTE''' if the file authorized_keys does not exist you will have to create it.		'''NOTE''' if the file authorized_keys does not exist you will have to create it.

Jab at 17:50, 15 January 2014

2014-01-15T17:50:38Z

← Older revision		Revision as of 11:50, 15 January 2014
Line 146:		Line 146:

	'''NOTE if the file ''authorized_keys'' did not exist and you had to create it you must make sure it has the right file permissions in this case 600 (eg -rw------- ).'''		'''NOTE if the file ''authorized_keys'' did not exist and you had to create it you must make sure it has the right file permissions in this case 600 (eg -rw------- ).'''

			[[Category:Troubleshooting]]
			[[Category:FAQ]]

Jab at 19:11, 4 March 2013

2013-03-04T19:11:10Z

← Older revision		Revision as of 13:11, 4 March 2013
Line 10:		Line 10:

	* Below we will take you though some of the basic step of creating SSH keys.		* Below we will take you though some of the basic step of creating SSH keys.



			'''NOTE if the file ''authorized_keys'' did not exist and you had to create it you must make sure it has the right file permissions in this case 600 (eg -rw------- ).'''

	===Linux===		===Linux===
Line 141:		Line 145:


	'''NOTE if the file ''authorized_keys'' did not exist and you had to create it you must make sure it has the right file permissions in this case 600 (eg -rw------- ).		'''NOTE if the file ''authorized_keys'' did not exist and you had to create it you must make sure it has the right file permissions in this case 600 (eg -rw------- ).'''