ubuntu-webapps-bugs team mailing list archive
-
ubuntu-webapps-bugs team
-
Mailing list archive
-
Message #04297
[Bug 1260103] Re: oxide should use an app-specific path for shared memory files
Re-opening for oxide as it turns out APP_PKGNAME is not an environment
variable that is being set anywhere for click apps. According to
https://developer.ubuntu.com/en/phone/platform/guides/app-confinement/,
its value can be inferred like this:
APP_PKGNAME = APP_ID.split('_')[0]
** Changed in: oxide
Status: Fix Released => Confirmed
--
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 Canonical System Image:
In Progress
Status in Oxide:
Confirmed
Status in webapps-sprint:
Fix Committed
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/canonical-devices-system-image/+bug/1260103/+subscriptions