Work for DBus

Registered by Jamie Strandboge

Acceptance criteria for June:
Goal: Users and developers can, with confidence, add DBus rules to AppArmor policy (ie, the language is finalized)

Acceptance criteria for July:
Goal: User can use a pre-release version of DBus with apparmor mediation
Goal: Users and developers can, with confidence, add DBus rules to AppArmor policy (ie, the language is finalized)

Acceptance criteria for August:
Goal: Users are able to run applications with DBus rules in effect

Blueprint information

Status:
Complete
Approver:
Jamie Strandboge
Priority:
High
Drafter:
John Johansen
Direction:
Approved
Assignee:
Tyler Hicks
Definition:
Approved
Series goal:
Accepted for saucy
Implementation:
Implemented
Milestone target:
milestone icon ubuntu-13.10
Started by
Jamie Strandboge
Completed by
Jamie Strandboge

Related branches

Sprints

Whiteboard

jdstrand> having kernel, apparmor and dbus in Ubuntu archive is not criteria for achieving June acceptance criteria

jdstrand, 2013-09-24> Plumbers revealed kdbus is coming along and upstream systemd is pushing for inclusion in the coming months. We need to make sure that our interests wrt AppArmor mediation are addressed. We need to work with other LSMs to make sure what is upstreamed is usable by our current mediation strategy

(?)

Work Items

Work items for ubuntu-13.07:
[tyhicks] drive language definition to completion: DONE
[tyhicks] update parser for language and ABI change: DONE
[tyhicks] DBus for ABI change: DONE
[tyhicks] push kernel to archive: DONE
[tyhicks] push apparmor to archive: DONE
[tyhicks] push dbus to archive: DONE

Work items for ubuntu-13.08:
[jdstrand] incorporate ubuntu-unity-* abstractions (ie, DBus policy) into easyprof templates/policy groups: DONE

Work items for ubuntu-13.09:
[sbeattie] support variables in the dbus rule post processor (LP: #1218099): DONE
[jdstrand] clean up existing ubuntu-unity-* abstractions: DONE

Work items for ubuntu-13.10:
[tyhicks] deep dive into current status of kdbus, libdbus, systemd's intended use of kdbus, etc (high) (5): INPROGRESS

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.