+1 for the migration and again apologies for reporting this as a bug. I'll send a PR on gitlab tomorrow. :)
Thanks! -- You received this bug notification because you are a member of AppArmor Developers, which is subscribed to AppArmor Profiles. https://bugs.launchpad.net/bugs/1732040 Title: [Pull-Request] Chromium browser on Enforce Status in AppArmor Profiles: Invalid Bug description: Apologies in advance, this is probably the wrong way to send a "Pull- Request" on launchpad. I've been using Chromium Browser on enforce for a couple of weeks. The default profile requires a couple of changes to make it usable. I thought to contribute them back: https://git.launchpad.net/~bbriniotis/apparmor-profiles/commit/ There are two main changes: 1. The chrome-sandbox gets memory map exec permissions to make Chromium run on enforce mode. 2. Gave ixr permissions to gio to make magnet links work. All the changes are made directly to the 18.04 folder. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor-profiles/+bug/1732040/+subscriptions -- AppArmor mailing list AppArmor@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
