apparmor_parser --namespace-string does not load profiles in the specified ns in 2.10

Bug #1526085 reported by Tyler Hicks on 2015-12-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AppArmor
High
Tyler Hicks
2.10
Undecided
Unassigned

Bug Description

AppArmor 2.10 contains a regression which causes profiles to not be loaded in a policy namespace even when the --namespace-string option is passed to apparmor_parser.

In 2.9.1:

$ echo "/t {}" | apparmor_parser -qSn mynamespace | strings
version
namespace
mynamespace
profile
flags
caps64
policydb
aadfa
notflex

In 2.10:

$ echo "/t {}" | apparmor_parser -qSn mynamespace | strings
version
profile
flags
caps64
policydb
aadfa
notflex

Note that the 2.10 binary policy output is missing the "namespace" and "mynamespace" fields.

Tyler Hicks (tyhicks) wrote :

Committed as revno 3287 in apparmor-2.10 and 3300 in apparmor trunk.

Changed in apparmor:
status: In Progress → Fix Committed
Christian Boltz (cboltz) on 2015-12-16
Changed in apparmor:
milestone: none → 2.11
Christian Boltz (cboltz) on 2017-01-10
Changed in apparmor:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers