Changes between Initial Version and Version 1 of SecureUpdates


Ignore:
Timestamp:
10/20/09 16:50:32 (15 years ago)
Author:
Christopher Small
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SecureUpdates

    v1 v1  
     1[[PageOutline]]
     2
     3== Project Number ==
     4
     51696
     6
     7== Project Title ==
     8
     9Exploiting Insecurity to Secure Software Update Systems[[BR]]
     10(a.k.a. SECUREUPDATES)
     11
     12=== Technical Contacts ===
     13
     14Justin Cappos <justinc@cs.washington.edu>
     15
     16=== Participating Organizations ===
     17
     18[http://www.cs.washington.edu Computer Science and Engineering][[BR]]
     19University of Washington[[BR]]
     20Box 352350
     21Seattle, WA 98195-2350
     22
     23=== GPO Liason System Engineer ===
     24
     25Christopher Small <chris@geni.net>
     26
     27== Scope ==
     28
     29This proposed effort will create a framework that secures the software
     30update systems that operate on GENI. The work will define and
     31implement a security layer that can operate over many different
     32application-specific installation environments, thus providing secure
     33update functions for diverse GENI nodes and clients. The proposal
     34plans to leverage the VM and the redirection proxy from the Million
     35Node GENI project to support multiple platforms. The effort provides
     36secure key management support for software update system developers,
     37allowing software updates to be signed, validated, and distributed
     38securely.
     39
     40=== Current Capabilities ===
     41
     42=== Milestones ===
     43
     44Nov 15, 2009
     45        Deliver short white paper or architecture document that explains the problem this project is attacking and outlines your solution, discussing how the work fits into GENI, what it will be used for, and how it will be used.
     46Dec 30, 2009
     47        Deliver a design document for client library protection against replay and freeze attacks.
     48        Deliver a design document for the repository library protection against replay and freeze attacks.
     49Mar 28, 2010
     50        Demonstrate client library implementation that protects against replay and freeze attacks for Linux.
     51        Demonstrate repository library implementation that protects against replay and freeze attacks.
     52May 30, 2010
     53        Demonstrate push mechanism that provides security metadata to the repository library.
     54        Make available the code for example client software update system implementation using the client library.
     55Sept 30, 2010
     56        Deliver a design document for client library selective trust delegation and key management.
     57        Deliver a design document for repository library selective trust delegation and key management.
     58
     59[[MilestoneDate(CMU Lab: S2.a)]] Short Milestone Description[[BR]]
     60
     61== Project Technical Documents ==
     62
     63=== Quarterly Status Reports ===
     64
     65due 31Dec09: [wiki:ProjTemp-4Q09-status 4Q09 Status Report]
     66
     67=== Spiral 2 Connectivity ===
     68
     69=== Related Projects ===
     70
     71[wiki:"ProvisioningService" Provisioning Service (Raven)][[BR]]