Application:SkyNet - Revision history

RodWhitby at 11:46, 23 May 2010

2010-05-23T11:46:40Z

RodWhitby at 11:45, 23 May 2010

2010-05-23T11:45:35Z

RodWhitby at 11:36, 23 May 2010

2010-05-23T11:36:22Z

RodWhitby at 06:14, 23 May 2010

2010-05-23T06:14:20Z

RodWhitby at 06:12, 23 May 2010

2010-05-23T06:12:09Z

RodWhitby at 06:10, 23 May 2010

2010-05-23T06:10:33Z

RodWhitby at 06:08, 23 May 2010

2010-05-23T06:08:30Z

Sbromwich at 03:03, 9 May 2010

2010-05-09T03:03:16Z

RodWhitby at 02:26, 9 May 2010

2010-05-09T02:26:58Z

RodWhitby at 02:26, 9 May 2010

2010-05-09T02:26:16Z

@@ Line 1: / Line 1: @@
 SkyNet is an application which manages the secure linking of webOS (and other) devices together over the internet.
-It uses secure exchange of ssh keys, and management of restricted command lines in the authorized_keys file, to allow secure, managed, authorized transfers of files between devices.
+It uses secure exchange of ssh keys, and management of restricted command lines in the authorized_keys file, to allow secure, managed, authorized communication between devices.
 It can also be used to set up secure tunnels and VPN networks of devices using openssh layer 3 tunnelling.

@@ Line 1: / Line 1: @@
 SkyNet is an application which manages the secure linking of webOS (and other) devices together over the internet.
-It uses secure exchange of ssh keys, and management of restricted rsync command lines in the authorized_keys file, to allow secure, managed, authorized transfers of files between devices.
+It uses secure exchange of ssh keys, and management of restricted command lines in the authorized_keys file, to allow secure, managed, authorized transfers of files between devices.
-It can also be used to set up secure tunnels and VPN networks of devices using openvpn.
+It can also be used to set up secure tunnels and VPN networks of devices using openssh layer 3 tunnelling.
 All actions must be carefully controlled and authorised by the user, lest it become the SkyNet of the Terminator variety ...
 Discussion welcome on how we achieve this.  Let's use this as a working page for architecture and design ideas.  Just write them below.
 == Service Methods ==
@@ Line 19: / Line 15: @@
 So an atomic service method to create a key-pair, and install the private key.  The service method must not give access to the private key.
-Then a second service method to return the public key for transmission to the remote device.
+Then a second service method to return the public key for transmission to the remote device.  Transmission can be over email.
 Security implications for the key-pair generation service method include denial of service by a rogue mojo app calling the service to create a new private key.  This can be countered by a confirmation screen like in the old Java Package Manager Service.

← Older revision		Revision as of 11:36, 23 May 2010
Line 24:		Line 24:

	No known security implications for the public key retrieval service method. One assumes that rogue mojo knowledge of a public key is not an issue (it's a public key by definition).		No known security implications for the public key retrieval service method. One assumes that rogue mojo knowledge of a public key is not an issue (it's a public key by definition).
		+
		+	== Encrypted Virtual Tunnels ==
		+
		+	We can use the layer-3 tunnelling features of OpenSSH 4.3 or later to create an encrypted virtual tunnel between the two hosts.
		+
		+	See https://help.ubuntu.com/community/SSH_VPN and http://wouter.horre.be/doc/vpn-over-ssh for details.
		+
		+	Initially a point-to-point connection will allow communication between two participating hosts.
		+
		+	This may be able to be extended to all hosts participating in SkyNet. We could perhaps use the 10.x.y.z address range, and use the last three octets of the wifi MAC address to guarantee uniqueness across the last three octets of the 10.x.y.z addressing range. The subnet would be 255.0.0.0 to allow routing between all participating hosts.

@@ Line 17: / Line 17: @@
 First we need a means of creating an ssh key-pair, and sending the public key to another device for installation there.
-So an atomic service method to create a key-pair, install the private key, and return the public key is needed.  The service method must not give access to the private key.
+So an atomic service method to create a key-pair, and install the private key.  The service method must not give access to the private key.
-Perhaps two service methods.  One to generate a key-pair, and one to return the public key.
+Then a second service method to return the public key for transmission to the remote device.
 Security implications for the key-pair generation service method include denial of service by a rogue mojo app calling the service to create a new private key.  This can be countered by a confirmation screen like in the old Java Package Manager Service.
 No known security implications for the public key retrieval service method.  One assumes that rogue mojo knowledge of a public key is not an issue (it's a public key by definition).

← Older revision		Revision as of 06:12, 23 May 2010
Line 21:		Line 21:
	Perhaps two service methods. One to generate a key-pair, and one to return the public key.		Perhaps two service methods. One to generate a key-pair, and one to return the public key.

−	Security implications include denial of service by a rogue mojo app calling the service to create a new private key. This can be countered by a confirmation screen like in the old Java Package Manager Service.	+	Security implications for the key-pair generation service method include denial of service by a rogue mojo app calling the service to create a new private key. This can be countered by a confirmation screen like in the old Java Package Manager Service.
		+
		+	No known security implications for the public key retrieval service method. One assumes that rogue mojo knowledge of a public key is not an issue (it's a public key by definition).

← Older revision		Revision as of 06:10, 23 May 2010
Line 20:		Line 20:

	Perhaps two service methods. One to generate a key-pair, and one to return the public key.		Perhaps two service methods. One to generate a key-pair, and one to return the public key.
		+
		+	Security implications include denial of service by a rogue mojo app calling the service to create a new private key. This can be countered by a confirmation screen like in the old Java Package Manager Service.

← Older revision		Revision as of 06:08, 23 May 2010
Line 12:		Line 12:

	Add some sort of profile support; eg if I am at work connected through wifi on the corporate SSID I don't want the Pre to attempt to VPN in to get to work resources, and conversely at home I don't want to tunnel to my home network if I am already attached by wifi.		Add some sort of profile support; eg if I am at work connected through wifi on the corporate SSID I don't want the Pre to attempt to VPN in to get to work resources, and conversely at home I don't want to tunnel to my home network if I am already attached by wifi.
		+
		+	== Service Methods ==
		+
		+	First we need a means of creating an ssh key-pair, and sending the public key to another device for installation there.
		+
		+	So an atomic service method to create a key-pair, install the private key, and return the public key is needed. The service method must not give access to the private key.
		+
		+	Perhaps two service methods. One to generate a key-pair, and one to return the public key.

← Older revision		Revision as of 03:03, 9 May 2010
Line 8:		Line 8:

	Discussion welcome on how we achieve this. Let's use this as a working page for architecture and design ideas. Just write them below.		Discussion welcome on how we achieve this. Let's use this as a working page for architecture and design ideas. Just write them below.
		+
		+	Add vpnc support.
		+
		+	Add some sort of profile support; eg if I am at work connected through wifi on the corporate SSID I don't want the Pre to attempt to VPN in to get to work resources, and conversely at home I don't want to tunnel to my home network if I am already attached by wifi.

← Older revision		Revision as of 02:26, 9 May 2010
Line 7:		Line 7:
	All actions must be carefully controlled and authorised by the user, lest it become the SkyNet of the Terminator variety ...		All actions must be carefully controlled and authorised by the user, lest it become the SkyNet of the Terminator variety ...

−	Discussion welcome on how we achieve this.	+	Discussion welcome on how we achieve this. Let's use this as a working page for architecture and design ideas. Just write them below.