desktop-packages team mailing list archive

[Seth Arnold <1374222@xxxxxxxxxxxxxxxxxx>]

Looks like we may need to adjust apparmor policy lines too. I wonder
what motivated the path change.

** Information type changed from Private Security to Public Security

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1374222

Title:
  path for policy files changed

Status in “apparmor” package in Ubuntu:
  New
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909
  and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917

  The path checked by Ubuntu's chromium-browser package for policy files
  has changed.  This results in administrator mandated settings not
  being applied, which should be considered a security vulnerability.

  In previous versions of the package, policy files were read from: /etc/chromium-browser/policies
  In the new version of the package, it is reading policy files from: /etc/chromium/policies

  The new package version has dropped the following line from its debian/rules file:
      sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \
          $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc

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