Maverick
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
Blueprints
All blueprints involving the security team:
BurnDown (for all blueprints)
Alpha-3: http://people.canonical.com/~pitti/workitems/maverick/canonical-security-maverick-alpha-3.html
- Entire cycle:
Weekly summary
(Updated manually once Beta hits, currently not being updated for Maverick)
We fixed 0 RC bugs, got 0 new ones.
Milestoned Bugs
Fixed last week:
600549: m2crypto fails to build from source in maverick
596136: package binutils-multiarch 2.20.1-3ubuntu6 failed to install/upgrade
Triaged problems:
545795: apparmor driver blocks access to hostdev and pcidev devices
578527: map serial port throws "chardev: opening backend "tty" failed"
Bugs which need better understanding/debugging:
599450: [apparmor] getattr handled incorrectly in 2.6.35-6.7
Planned changes for Final
- None
Deferred for SRU
- None
Other Maverick-targeted bugs
- None