Sziráki, thanks for filing this bug. I've reviewed your logs and can't
figure out what exactly is wrong:
- Your kernel logs shows over 18000 DENIED accesses requested by
processes executing with a profile that matches
'profile="/usr/lib/firefox/'. Thus it certainly appears that much of
Firefox is executing while confined. Can you provide ps auxwZ output
that shows firefox processes that aren't executing in their profile?
- Your aa-status output shows that Chromium is executing in complain
mode.
- Note that the default AppArmor profile for Firefox is in fact very
permissive. See the /etc/apparmor.d/abstractions/ubuntu-browsers.d/user-
files file for the rules involved.
Can you please identify more concretely what is happening that you feel
is a bug?
Thanks
** Changed in: apparmor (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661523
Title:
AppArmor profile for Firefox (51.0.1) after took in enforced mode
falls back into unconfined
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1661523/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
