Introduction
Security team development (ie specification work) is done as time allows. This page does not include security updates, audits, investigations, etc. This page only includes information on proactive development work as it pertains to the Ubuntu Release schedule. Blueprints that the security team is committed to completing in a development cycle have an 'Essential' priority.
Specifications
Essential blueprints
Blueprint |
Design |
Delivery |
Assignee |
Approved |
Implemented |
Jamie Strandboge (jdstrand) |
|
Approved |
Implemented |
Kees Cook (kees) |
|
Approved |
Implemented1 |
Jamie Strandboge (jdstrand) |
|
Approved |
Implemented |
Marc Deslauriers (mdeslaur) |
|
Approved |
Implemented |
Jamie Strandboge (jdstrand) |
- Most was implemented for Lucid, but one part had to be deferred to Maverick (properly support save/restore, but the karmic workaround is still in effect). All has been upstreamed and the merge from Debian is ready for Maverick.
Other blueprints
Security team originated blueprints:
Blueprints involving the security team:
BurnDown (for all blueprints)
Entire cycle: http://people.canonical.com/~pitti/workitems/canonical-security.html
Alpha-3: http://people.canonical.com/~pitti/workitems/canonical-security-lucid-alpha-3.html
Old breakdown: http://piware.de/workitems/security/lucid/report.html
Weekly summary
(Updated manually once Beta hits, currently not being updated for Lucid)
We fixed 0 RC bugs, got 0 new ones.
Milestoned Bugs
Fixed last week:
- None
Triaged problems:
- None
Bugs which need better understanding/debugging:
- None
Planned changes for Final
- None
Deferred for SRU
- None
Other Lucid-targeted bugs
- None