Searched hist:"86684240 eb5753bb97c2cfc93d1d25fa1870f8f1" (Results 1 - 2 of 2) sorted by relevance

/frameworks/base/data/etc/
H A Dplatform.xmldiff 86684240eb5753bb97c2cfc93d1d25fa1870f8f1 Sat Feb 03 23:32:31 CET 2018 Jeff Sharkey <jsharkey@android.com> Media process should run with "write" access.

The WRITE_MEDIA_STORAGE permission had inadvertently been giving apps
the "default" view of storage. This had worked for a long since,
since we also gave them the "sdcard_rw" permission, but a recent
security patch broke this for secondary users.

Apps holding this permission should have been mounted "write" all
along, and relied on that view to access storage devices. This also
means they no longer need the "sdcard_rw" GID.

Test: builds, boots, secondary user media/camera works
Bug: 72732906, 71737806, 72224817
Change-Id: I5cd687a1e128024f33b4acd93c15e75192ed1c85
/frameworks/base/services/core/java/com/android/server/pm/
H A DPackageManagerService.javadiff 86684240eb5753bb97c2cfc93d1d25fa1870f8f1 Sat Feb 03 23:32:31 CET 2018 Jeff Sharkey <jsharkey@android.com> Media process should run with "write" access.

The WRITE_MEDIA_STORAGE permission had inadvertently been giving apps
the "default" view of storage. This had worked for a long since,
since we also gave them the "sdcard_rw" permission, but a recent
security patch broke this for secondary users.

Apps holding this permission should have been mounted "write" all
along, and relied on that view to access storage devices. This also
means they no longer need the "sdcard_rw" GID.

Test: builds, boots, secondary user media/camera works
Bug: 72732906, 71737806, 72224817
Change-Id: I5cd687a1e128024f33b4acd93c15e75192ed1c85

Completed in 1468 milliseconds