ubuntu-webapps-bugs team mailing list archive

Thread
Date

[Bug 1260103] Re: oxide should use an app-specific path for shared memory files

To: ubuntu-webapps-bugs@xxxxxxxxxxxxxxxxxxx
From: Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>
Date: Fri, 22 Jul 2016 11:54:14 -0000
Reply-to: Bug 1260103 <1260103@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This is now fixed in oxide, the apparmor-easyprof-ubuntu counterpart
needs to be implemented.

** Changed in: oxide
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1260103

Title:
  oxide should use an app-specific path for shared memory files

Status in Oxide:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This results in an AppArmor rule like the following:
    owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1260103/+subscriptions