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

Bug #1526085 reported by Tyler Hicks
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AppArmor
Fix Released
High
Tyler Hicks
2.10
Fix Released
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.

Revision history for this message
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)
Changed in apparmor:
milestone: none → 2.11
Christian Boltz (cboltz)
Changed in apparmor:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.