desktop-packages team mailing list archive

[Seth Arnold <1374222@xxxxxxxxxxxxxxxxxx>]

Browsers are special. We certainly don't have the resources to fix only
security issues found in the browsers as we do with most other packages.
We package what upstream produces and this is far from the first thing
they've moved: the name of the sandbox executable has changed three or
four times since I've been paying attention and I wouldn't be surprised
if they change it again in the future. Overall, the benefits of shipping
recent browsers with recent features and recent fixes works out for the
best but it doesn't fit the traditional LTS mold well.

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