SSH Tutorial - Revision history

Digimer at 19:44, 1 May 2011

2011-05-01T19:44:42Z

Digimer: /* What to do */

2010-06-03T18:39:02Z

What to do

← Older revision		Revision as of 18:39, 3 June 2010
Line 35:		Line 35:
	(Yes, that is my real public key... It won't do you much good though. ;) ).		(Yes, that is my real public key... It won't do you much good though. ;) ).

	Copy the output and then ssh normally into the remote machine.		Copy the output and then <span class="code">ssh</span> normally into the remote machine.

	<source lang="bash">		<source lang="bash">
Line 41:		Line 41:
	</source>		</source>

	Once you've logged in with the password, create/edit the the <span class="code">~/.ssh/authorized_keys</span> file ~~and paste~~ the contents of your <span class="code">~/.ssh/id_rsa.pub</span> file on a new line. Save the file and then log out of the remote host.		Once you've logged in with the password, create/edit the the <span class="code">~/.ssh/authorized_keys</span> file:
			<source lang="bash">
			vim ~/.ssh/authorized_keys
			</source>

			Paste the contents of your <span class="code">~/.ssh/id_rsa.pub</span> file on a new line. Save the file and then log out of the remote host. You should now be able to reconnect exactly as you did a moment ago, but this time you will not be prompted for a password.

	~~Done.~~ You ~~should now be able to reconnect exactly~~ as you ~~did a moment ago, but this time you will not be prompted for a password~~.		You can copy this public key into as many destination machines/users as you would like.

	== A Note ==		== A Note ==

Digimer: /* What to do */

2010-06-03T18:34:22Z

What to do

← Older revision		Revision as of 18:34, 3 June 2010
Line 27:		Line 27:
	cat ~/.ssh/id_rsa.pub		cat ~/.ssh/id_rsa.pub
	</source>		</source>

			It should output something like this:
			<source lang="text">
			ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEArp8VPicZjSglhDI7NhzwdGH6/tHPPk1uKJ6fBCWSoCA/nVyuPvah2wdNKfHBmdG0iDUG49mSIAX71UdPZrLKuOjCks79bCdMSj+Zea5c61RMB0w2GuhY+wAKM+C+GjYvB6j+Ft2jRKw3YoVVmYBf/iW9oBuOH9dIBAIAfOpd3TrJJef+1JmkPVfU3dnn5K+ZfDZNv+7z2Fa2UznOXWkEN/tdqdXTp5X7UJH8gOVHQky5DPgtev7a0u+Emayd4UzHhgfY4pIfB3g46NpvN36GGwdIA3FdwlYUgmXqTpJnyPFlWpKPcnDTlrdcHhgoejvOe6M4HqykxoL49ok1QCEEkQ== digimer@lework
			</source>

			(Yes, that is my real public key... It won't do you much good though. ;) ).

	Copy the output and then ssh normally into the remote machine.		Copy the output and then ssh normally into the remote machine.

Digimer: /* Source Machine and User */

2010-06-03T18:30:42Z

Source Machine and User

← Older revision		Revision as of 18:30, 3 June 2010
Line 13:		Line 13:
	This is meant to be a dead-simple example of how to create a shared key to avoid the need for passwords. Nothing more. In the same vein, it is expected that you understand the potential security implications of doing so.		This is meant to be a dead-simple example of how to create a shared key to avoid the need for passwords. Nothing more. In the same vein, it is expected that you understand the potential security implications of doing so.

	= ~~Source Machine and User~~ =		= What to do =

	On the source machine, as the user you will make the ssh call as, run:		On the source machine, as the user you will make the ssh call as, run:

Digimer at 18:30, 3 June 2010

2010-06-03T18:30:27Z

← Older revision		Revision as of 18:30, 3 June 2010
Line 8:		Line 8:

	This shows how to have the two servers accept each other's SSH keys without the need for passwords. This allows for, among other things, to shuffle data between two servers securely using 'rsync'.		This shows how to have the two servers accept each other's SSH keys without the need for passwords. This allows for, among other things, to shuffle data between two servers securely using 'rsync'.

	~~== A Note ==~~

	Keys you generate will only work when connecting from the source computer as the user you created the key as. For example, if you create the key as <span class="code">root</span> and then try to connect as <span class="code">someuser</span>, the key will not be used. You would need to create another key as <span class="code">someuser</span>.

	~~Likewise, where you put the public key on the destination server will define which user you can connect as on the remote machine.~~

	== Scope ==		== Scope ==
Line 43:		Line 37:

	Done. You should now be able to reconnect exactly as you did a moment ago, but this time you will not be prompted for a password.		Done. You should now be able to reconnect exactly as you did a moment ago, but this time you will not be prompted for a password.

			== A Note ==

			Keys you generate will only work when connecting from the source computer as the user you created the key as. For example, if you create the key as <span class="code">root</span> and then try to connect as <span class="code">someuser</span>, the key will not be used. You would need to create another key as <span class="code">someuser</span>.

			Likewise, where you put the public key on the destination server will define which user you can connect as on the remote machine.

	{{footer}}		{{footer}}

Digimer: Created page with '{{howto_header}} '''Note''': This needs work. ---- = Password-less Inter-server Communication = This shows how to have the two servers accept each other's SSH keys without th…'

2010-06-03T18:29:04Z

Created page with '{{howto_header}} '''Note''': This needs work. ---- = Password-less Inter-server Communication = This shows how to have the two servers accept each other's SSH keys without th…'

Páàjì titun

{{howto_header}}

'''Note''': This needs work.

----

= Password-less Inter-server Communication =

This shows how to have the two servers accept each other's SSH keys without the need for passwords. This allows for, among other things, to shuffle data between two servers securely using 'rsync'.

== A Note ==

Keys you generate will only work when connecting from the source computer as the user you created the key as. For example, if you create the key as root and then try to connect as someuser, the key will not be used. You would need to create another key as someuser.

Likewise, where you put the public key on the destination server will define which user you can connect as on the remote machine.

== Scope ==

This is meant to be a dead-simple example of how to create a shared key to avoid the need for passwords. Nothing more. In the same vein, it is expected that you understand the potential security implications of doing so.

= Source Machine and User =

On the source machine, as the user you will make the ssh call as, run:
<source lang="bash">
ssh-keygen -t rsa
</source>

Accept the default value for the prompts.

You should now see two new files; '~/.ssh/id_rsa' and '~/.ssh/id_rsa.pub'. Open the public key file:

<source lang="bash">
cat ~/.ssh/id_rsa.pub
</source>

Copy the output and then ssh normally into the remote machine.

<source lang="bash">
ssh someuser@somehost
</source>

Once you've logged in with the password, create/edit the the ~/.ssh/authorized_keys file and paste the contents of your ~/.ssh/id_rsa.pub file on a new line. Save the file and then log out of the remote host.

Done. You should now be able to reconnect exactly as you did a moment ago, but this time you will not be prompted for a password.

{{footer}}