Radarcape:SSH Tunneling - Revision history

imported>Beastadmin at 19:25, 25 March 2015

2015-03-25T19:25:58Z

← Older revision		Revision as of 19:25, 25 March 2015
Line 1:		Line 1:
	~~__TOC__~~

	{\|		{\|
	\|[[File:Expert.png\|For Experts]]		\|[[File:Expert.png\|For Experts]]
	\|''~~The tasks described in~~ this ~~manual require advanced skills in Unix/Linux.~~''		\|''Required Linux/Unix skills to execute this task: Advanced''
	\|}		\|}

			__TOC__

	=SSH Tunneling Howto=		=SSH Tunneling Howto=

imported>Dl4mea: /* Radarcape essentials */

2013-12-15T07:46:14Z

Radarcape essentials

← Older revision		Revision as of 07:46, 15 December 2013
Line 33:		Line 33:
	dropbearkey -t rsa -f ~/.ssh/id_rsa -y		dropbearkey -t rsa -f ~/.ssh/id_rsa -y
	</source>		</source>
	* set attributes of ~, .ssh and authorized_keys to 600.		* set attributes of ~, .ssh and authorized_keys to 600
			* check that on the Radarcape the /home/root is also owned by user root. Recently it occured sometimes that xroot:xroot was the owner
			<source lang="bash">
			chown root:root /home/root
			</source>


	The file id_rsa is the so called <ins>private key</ins>, a file which never should leave your room. You should not transfer it over public lines. Another information, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be inserted into the file ~/.ssh/authorized_keys on the computer you want to connect (aka server). This phrase is safe to be published.		The file id_rsa is the so called <ins>private key</ins>, a file which never should leave your room. You should not transfer it over public lines. Another information, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be inserted into the file ~/.ssh/authorized_keys on the computer you want to connect (aka server). This phrase is safe to be published.

imported>Dl4mea: /* Radarcape essentials */

2013-12-12T07:16:57Z

Radarcape essentials

← Older revision		Revision as of 07:16, 12 December 2013
Line 35:		Line 35:
	* set attributes of ~, .ssh and authorized_keys to 600.		* set attributes of ~, .ssh and authorized_keys to 600.

	The file id_rsa is the so called <ins>private key</ins>, a file which never should leave your room. Another ~~line~~, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be inserted into the file ~/.ssh/authorized_keys on the computer you want to connect (aka server).		The file id_rsa is the so called <ins>private key</ins>, a file which never should leave your room. You should not transfer it over public lines. Another information, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be inserted into the file ~/.ssh/authorized_keys on the computer you want to connect (aka server). This phrase is safe to be published.

	===== Server essentials =====		===== Server essentials =====

imported>Dl4mea: /* Server essentials */

2013-12-12T07:14:04Z

Server essentials

← Older revision		Revision as of 07:14, 12 December 2013
Line 41:		Line 41:
	The server is the common connection point for the user and the Radarcape. It is not necessarily a computer for its own, it can even be the computer that hosts the PC application, or even a Radarcape by its own.		The server is the common connection point for the user and the Radarcape. It is not necessarily a computer for its own, it can even be the computer that hosts the PC application, or even a Radarcape by its own.

	Copy the public key given from above command to the server folder ~/.ssh/authorized_keys. Maybe you need to use an editor in order to edit the given single line public key to an existing file. Mind that the attributes of ~, .ssh and authorized_keys are set to 600. If correctly done, you must be able to login via ssh from the Radarcape to the server without entering a password. As long as this does not work, there is still some fault.		Copy the public key given from above command to the server folder ~/.ssh/authorized_keys. Maybe you need to use an editor in order to edit the given single line public key to an existing file. Mind that the attributes of ~, .ssh and authorized_keys are set to 600.<br>If correctly done, you must be able to login via ssh from the Radarcape to the server without entering a password. As long as this does not work, there is still some fault. dropbear ssh, which is used on the Radarcape, does not automatically use the ssh keys. Therefore, you need to specify

			<source lang="bash">
			ssh -i ~/.ssh/id_rsa <your_servername_or_ip>
			</source>

	===== Radarcape 2nd step =====		===== Radarcape 2nd step =====

imported>Dl4mea: /* Radarcape essentials */

2013-12-12T07:11:05Z

Radarcape essentials

← Older revision		Revision as of 07:11, 12 December 2013
Line 35:		Line 35:
	* set attributes of ~, .ssh and authorized_keys to 600.		* set attributes of ~, .ssh and authorized_keys to 600.

	The file id_rsa is the so called <ins>private key</ins>, a file which never should leave your room. Another line, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be inserted into the file ~/.ssh/authorized_keys on the computer you want to connect (aka server). Please ensure that access rights for ~, .ssh and authorized_keys on the server are also set to 0600 or 0700. The format of authorized_keys entries is different when using openssh, but that is self explaining.		The file id_rsa is the so called <ins>private key</ins>, a file which never should leave your room. Another line, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be inserted into the file ~/.ssh/authorized_keys on the computer you want to connect (aka server).

	~~After editing authorized_keys on the server, try to logon from your local Radarcape to the server~~.

	===== Server essentials =====		===== Server essentials =====

imported>Dl4mea: /* Radarcape essentials */

2013-12-12T07:09:49Z

Radarcape essentials

← Older revision		Revision as of 07:09, 12 December 2013
Line 25:		Line 25:

	* Generate a SSH key pair on the local Radarcape		* Generate a SSH key pair on the local Radarcape
	cd ~/.ssh		<source lang="bash">
	dropbearkey -t rsa -f id_rsa		cd ~/.ssh
			dropbearkey -t rsa -f id_rsa
			</source>
			* note the given public key string. If forgotten, you may later retrieve it with
			<source lang="bash">
			dropbearkey -t rsa -f ~/.ssh/id_rsa -y
			</source>
	* set attributes of ~, .ssh and authorized_keys to 600.		* set attributes of ~, .ssh and authorized_keys to 600.

	The file id_rsa is the so called private key, a file which never should leave your room. Another line, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be ~~installed~~ on the computer you want to connect (aka server). ~~If ever you forget~~ the ~~public key~~, ~~''dropbearkey -t rsa -f ~/~~.~~ssh/id_rsa -y'' will again show~~ the ~~matching public key~~.		The file id_rsa is the so called <ins>private key</ins>, a file which never should leave your room. Another line, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be inserted into the file ~/.ssh/authorized_keys on the computer you want to connect (aka server). Please ensure that access rights for ~, .ssh and authorized_keys on the server are also set to 0600 or 0700. The format of authorized_keys entries is different when using openssh, but that is self explaining.

			After editing authorized_keys on the server, try to logon from your local Radarcape to the server.

	===== Server essentials =====		===== Server essentials =====

imported>Dl4mea: /* Server essentials */

2013-11-24T19:35:03Z

Server essentials

← Older revision		Revision as of 19:35, 24 November 2013
Line 33:		Line 33:
	===== Server essentials =====		===== Server essentials =====

	The server is the common connection point for the user and the Radarcape. It is not necessarily a computer for its own, it can even be the computer that hosts the PC application, or ~~another~~ Radarcape.		The server is the common connection point for the user and the Radarcape. It is not necessarily a computer for its own, it can even be the computer that hosts the PC application, or even a Radarcape by its own.

	Copy the public key given from above command to the server folder ~/.ssh/authorized_keys. Maybe you need to use an editor in order to edit the given single line public key to an existing file. Mind that the attributes of ~, .ssh and authorized_keys are set to 600. If correctly done, you must be able to login via ssh from the Radarcape to the server without entering a password. As long as this does not work, there is still some fault.		Copy the public key given from above command to the server folder ~/.ssh/authorized_keys. Maybe you need to use an editor in order to edit the given single line public key to an existing file. Mind that the attributes of ~, .ssh and authorized_keys are set to 600. If correctly done, you must be able to login via ssh from the Radarcape to the server without entering a password. As long as this does not work, there is still some fault.

imported>Dl4mea: /* Radarcape essentials */

2013-11-24T19:34:19Z

Radarcape essentials

← Older revision		Revision as of 19:34, 24 November 2013
Line 24:		Line 24:
	===== Radarcape essentials =====		===== Radarcape essentials =====

	~~First, generate~~ a SSH key pair on the local Radarcape		* Generate a SSH key pair on the local Radarcape
	cd ~/.ssh		cd ~/.ssh
	dropbearkey -t rsa -f id_rsa		dropbearkey -t rsa -f id_rsa
	~~Set~~ attributes of ~, .ssh and authorized_keys ~~are set~~ to 600.		* set attributes of ~, .ssh and authorized_keys to 600.

	The file id_rsa is the so called private key, a file which never should leave your room. Another line, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be installed on the computer you want to connect (aka server). If ever you forget the public key, ''dropbearkey -t rsa -f ~/.ssh/id_rsa -y'' will again show the matching public key.		The file id_rsa is the so called private key, a file which never should leave your room. Another line, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be installed on the computer you want to connect (aka server). If ever you forget the public key, ''dropbearkey -t rsa -f ~/.ssh/id_rsa -y'' will again show the matching public key.

imported>Dl4mea: /* Radarcape essentials */

2013-10-24T14:44:44Z

Radarcape essentials

← Older revision		Revision as of 14:44, 24 October 2013
Line 28:		Line 28:
	dropbearkey -t rsa -f id_rsa		dropbearkey -t rsa -f id_rsa
	Set attributes of ~, .ssh and authorized_keys are set to 600.		Set attributes of ~, .ssh and authorized_keys are set to 600.

			The file id_rsa is the so called private key, a file which never should leave your room. Another line, the so public key, which most probable starts with ''ssh-rsa AAAAB3NzaC1y'' and ends with ''root@radarcape'', needs to be installed on the computer you want to connect (aka server). If ever you forget the public key, ''dropbearkey -t rsa -f ~/.ssh/id_rsa -y'' will again show the matching public key.

	===== Server essentials =====		===== Server essentials =====

imported>Beastadmin at 19:09, 6 October 2013

2013-10-06T19:09:20Z

← Older revision		Revision as of 19:09, 6 October 2013
Line 1:		Line 1:
			__TOC__

			{\|
			\|[[File:Expert.png\|For Experts]]
			\|''The tasks described in this manual require advanced skills in Unix/Linux.''
			\|}

			=SSH Tunneling Howto=

	Imagine you know a remote location with internet access, someway far off and not reachable from your home network, where you like to place a Radarcape. Unfortunately this network is not directly accessible from your home network, as no domain name (like modesbeast.com) is given to it. In that case you can let the Radarcape establish a tunnel connection to a known address, reachable by both, the user and the Radarcape. Such a SSH tunnel is secured by SSH, and this is the common way in networking.		Imagine you know a remote location with internet access, someway far off and not reachable from your home network, where you like to place a Radarcape. Unfortunately this network is not directly accessible from your home network, as no domain name (like modesbeast.com) is given to it. In that case you can let the Radarcape establish a tunnel connection to a known address, reachable by both, the user and the Radarcape. Such a SSH tunnel is secured by SSH, and this is the common way in networking.