[apparmor] [Bug 1732040] Re: [Pull-Request] Chromium browser on Enforce

Tyler Hicks tyhicks at canonical.com
Mon Nov 13 23:40:36 UTC 2017


Hello and thanks for contacting us. We just migrated the AppArmor code
hosting from Launchpad to GitLab a week or two ago. Would it be possible
for you to create a merge request in GitLab against the apparmor-
profiles project?

  https://gitlab.com/apparmor/apparmor-profiles

Here's some info from GitLab on how to create merge requests:

  https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html

Let us know if this isn't possible for you and we can figure something
else out. Thanks!

** Changed in: apparmor-profiles
       Status: New => Invalid

-- 
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



More information about the AppArmor mailing list