| 1 | [[PageOutline]] |
| 2 | |
| 3 | = SecureUpdates Project Status Report = |
| 4 | |
| 5 | Period: 4Q09 |
| 6 | == I. Major accomplishments == |
| 7 | |
| 8 | === A. Milestones achieved === |
| 9 | N/A |
| 10 | |
| 11 | === B. Deliverables made === |
| 12 | SECUREUPDATES: S2.a overview (Due Nov 15th, 2009) |
| 13 | '''Sent on Nov 12th, 2009''' |
| 14 | |
| 15 | SECUREUPDATES: S2.b client lib design (Due Dec 30, 2009) |
| 16 | '''Sent on Dec 30th, 2009''' |
| 17 | |
| 18 | SECUREUPDATES: S2.c repo lib design (Due 12/30/09) |
| 19 | '''Sent on Dec 30th, 2009''' |
| 20 | |
| 21 | == II. Description of work performed during last quarter == |
| 22 | |
| 23 | === A. Activities and findings === |
| 24 | We produced an overall design document describing the security approach and goals of the |
| 25 | project. We produced design documents for a software updater that protects against replay |
| 26 | and freeze attacks. We also wrote a design document for a repository that provides the |
| 27 | necessary signed metadata and is resilient to attack. |
| 28 | === B. Project participants === |
| 29 | Justin Cappos (PI) |
| 30 | |
| 31 | Justin Samuel (Programmer) |
| 32 | === C. Publications (individual and organizational) === |
| 33 | None |
| 34 | === D. Outreach activities === |
| 35 | None |
| 36 | === E. Collaborations === |
| 37 | We had some preliminary discussions with the Raven and Tor folks to determine how our |
| 38 | efforts fit into their projects. |
| 39 | === F. Other Contributions === |
| 40 | We discussed our progress at GEC 6 and gave a talk in the Cluster B meeting. |