I hadn't realized that pulseaudio was no longer setuid, I'm just out of
date I suppose haha. If it's not setuid there's less of a need for such
strict rules, and using an abstraction may be ok.
But wouldn't it simply be enough to use: @{multiarch} ?
I apologize for taking so long to reply.
If /base were used I think this profile could be deployed across
architectures without issue, yes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094789
Title:
Pulseaudio Profile
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1094789/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
