Changes between Version 12 and Version 13 of SCU

Timestamp:

Oct 6, 2010, 9:28:23 AM (14 years ago)

Author:

fornasiero

Comment:

--

SCU

@@ -3 +3 @@
 TODO:
 * Upload SCU software package
-* Test procedure on other environments
 
 This document includes instructions how to install and to run the Secure Code Update protocol.
@@ -10 +9 @@
 
 == Introduction ==
+
+Updating the code running on Wireless Sensor Network (WSN) nodes is a necessary service, which can be used to remove bugs or to add new functionalities after the sensors have been deployed.
+In open, public, untrusted, or even hostile environments, protecting the code update operation against adversarial interference is an essential requirement. Otherwise, an insecure code update may provide an adversary with a backdoor rendering any security mechanism useless, and may even become a serious risk for the owner.
+There are mainly three security aspects to be considered in the desing of a Secure Code Update (SCU) mechanism. First, a SCU mechanism shall only allow the load of authentic code images into the nodes' memory. Second, a SCU mechanism must detect the dissemination of a modified or corrupted code image as early as possible. The need is to avoid unnecessary energy consumption due to the propagation of a corrupted image over multiple hops and to the re-transmission of its pages. Finally, a SCU mechanism must keep the secrecy of a code image being disseminated. The need is to prevent eavesdroppers from gaining information on the content of the code image.
 
 == Architectural Overview ==
@@ -18 +21 @@
 Installing the SCU protocol requires the following hardware tools and software packages:
 
- * [http://www.ubuntu.com/ Linux PC] This guide has been tested using Ubuntu 8.10 and 10.04
+ * [http://www.ubuntu.com/ Linux PC (Ubuntu)]
  * [http://docs.tinyos.net/index.php/Getting_started TinyOS-2.x SDK] 
  * SCU software package
  * At least 2 TelosB sensor nodes
 
-
-Appunti:
-Config files in 
-CONFIG_FILE=HOME_PATH+"/synapse-config.txt";
-SECRET_KEYS_FILE=HOME_PATH+"/synapse-secret-keys.xml";
-PUBLIC_KEYS_FILE=HOME_PATH+"/synapse-public-keys.bin";
-
-Security bits configured during deployment
+We assume that the installation PC is running a '''Linux''' operating system  and the [http://docs.tinyos.net/index.php/Getting_started TinyOS-2.x] has been installed and configured properly on it. We skip the installation of TinyOS here and refer to [http://docs.tinyos.net/index.php/Getting_started TinyOS-2.x] if needed. We describe the installation and configuration steps in the following for the [http://www.ubuntu.com/ Ubuntu] operating system.
+
+These is the structure of the files contained in the SCU software package:
+* scu
+** lib: Contains Bouncy Castle java library
+** scu-contrib: Contains developed TinyOS code for Secure Code Update
+** tinyos-2.x: Contains a minimal TinyOS source tree, necessary for compilation and running of the developed software
+** init_variables.sh: Inits environment variables
+** quick_start.sh: Simple script that execute a guided step-by step deployment, followed by a Secure Code Update operation.
+
 
 == Running a Secure Code Update session ==
 
-=== Folder structure 
-{{{
-scu
- |
- +-- lib
- |     Contains Bouncy Castle java library
- |
- +-- scu-contrib
- |     Contains developed TinyOS code for Secure Code Update
- |
- +-- tinyos-2.x
- |     Contains a minimal TinyOS source tree, necessary for compilation and running of the developed software
- |
- +-- init_variables.sh
- |      Inits environment variables
- +-- quick_start.sh
-        Simple script that execute a guided step-by step deployment, followed by a Secure Code Update operation.
-}}}
+
 === Shortest HOWTO: