Marking the Snappy task as "Wont't Fix" for now. This theoretically
could be fixed in snapd's home interface by dropping the "owner" prefix
but I don't think that's the correct fix for this bug. Either
libapparmor or the kernel need to handle the owner conditional better or
the calling application should do another query for owned files.
** Changed in: snappy
Status: New => Won't Fix
** Summary changed:
- libapparmor's aa_query_label() always returns allowed = 0 for snaps
+ libapparmor's aa_query_label() always returns allowed = 0 for file rules
containing the "owner" conditional
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620635
Title:
libapparmor's aa_query_label() always returns allowed = 0 for file
rules containing the "owner" conditional
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
