Find a way to move device specific apparmor rules into android/device tarball without breaking cache
Bug #1373412 reported by
Ricardo Salveti
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| android (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| lxc-android-config (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
Currently we're still handling device specific apparmor rules in lxc-android-config, and the main reason is that we need such rules when generating the cache for apparmor (which happens when generating the rootfs).
Moving the rules into the device tarball can cause timestamp issues if the cache is newer, as apparmor will never update the cache files with the device specific rules.
| Changed in lxc-android-config (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| tags: | added: application-confinement |
To post a comment you must log in.
