Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad
** Description changed:
- When using apparmor variables for the mountpoint in mount rules, the
+ When using apparmor tunaables for the mountpoint in mount rules, the
parser will parse the rule but the kernel blocks it.
Eg, this works:
- # works
- mount -> /home/*/mnt/,
+ # works
+ m
FYI, this came up in another snapd context in support of snap parallel
installs. It is worked around, but would be nice if this was fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launch
** Attachment added: "apparmor.profile"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1612393/+attachment/4719283/+files/apparmor.profile
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https:
This is the type of rule I'm striving to have:
mount fstype=fuse.* [^/]** ->
@{HOME}/snap/@{SNAP_NAME}/@{SNAP_REVISION}/{,**/},
That doesn't work, but his does:
mount fstype=fuse.* [^/]** ->
/home/*/snap/@{SNAP_NAME}/@{SNAP_REVISION}/{,**/},
--
You received this bug notification because you ar
** Attachment added: "fusexmp.c"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1612393/+attachment/4719282/+files/fusexmp.c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchp
6 matches
Mail list logo
