UtilityProcessHost::SetExposedDir doen't work on Android
Reported by
kuznetso...@gmail.com,
Apr 5 2016
|
|||
Issue descriptionSteps to reproduce the problem: Try to read existent file from exposed dir in utility process What is the expected behavior? File read succeed What went wrong? File read failed with 'no access' error Did this work before? No Chrome version: 47.0.2526.111 Channel: n/a OS Version: Flash Version: I think it is impossible (with Android api) to allow restricted file access from isolated (android:isolatedProcess=true) service. So two solutions are possible: 1) Remove SetExposedDir and DisableSandbox from UtilityProcessHost for Android 2) Launch PrivilegedProcessService instead of SandboxedProcessService if exposed dir was set.
,
Apr 11 2016
What is planned to run in the utilityProcess in this case?
,
Apr 12 2016
We plan to verify and unpack to |exposed_dir| zip-archives, previously downloaded from untrusted source (internet).
,
Apr 12 2016
For what feature in Chrome?
,
Apr 12 2016
I'm not Chrome developer, it will be a feature of third-party chromium-based application. But UtilityProcessHost::SetExposedDir is a public api of content module, and it doesn't work on Android. I think it may be unexpectedly for Chrome developers too.
,
Apr 13 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 9 2018
SetExposedDir doesn't work on several platforms, and there not a way to make this work for arbitrary directories on Android because of SELinux policies. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ppolise...@chromium.org
, Apr 11 2016Status: Available (was: Unconfirmed)