[Bug 1914148] Re: Firefox connstantly disabled on Apparmor

[Seth Arnold]

The Firefox AppArmor profile isn't enabled by default because it forces
the user to change how they interact with their browser.

Consider that the profile really allows downloads only into ~/Downloads/
directories. (There's other places that are writable, but even less
suitable for downloads.) Many users prefer to download directly to their
existing directory structure.

Consider the wide variety of plugins that may supply helper executables.
Plugins failing without a good interface in the browser to know why they
have failed would be very confusing.

Consider the huge number of applications that people install to handle
mime types. People want to be able to click a link to any random file
and have the browser offer to launch the helper.

People who are fine with all these impositions in how they can use
Firefox can enable the Firefox profile. They'll know how to debug issues
when they arise, and furthermore, probably already have a workflow that
makes it easy to work with the AppArmor policy restrictions.

But most Ubuntu users are completely unaware that they're running
AppArmor on many of their services. Surely some of this group would like
to use it more, if only they knew about it, but also many people just
need their computers to keep working as they always have.

If we enable this one profile, we run the serious risk that users will
disable AppArmor entirely.

Thanks

** Package changed: apparmor (Ubuntu) => firefox (Ubuntu)

-- 
You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1914148

Title:
  Firefox connstantly  disabled on Apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914148/+subscriptions