Open
Bug 1362579
Opened 7 years ago
Updated 2 years ago
Add sandboxing to the VR process
Categories
(Core :: WebVR, enhancement)
Core
WebVR
Tracking
()
NEW
People
(Reporter: kip, Unassigned)
References
Details
In Bug 1362578, we are moving the VRManager functionality to its own process. This will allow more restrictive sandboxing rules to be applied to the GPU process as the rules required for the Oculus and OpenVR runtimes can be applied separately to the new VR process. We are working with external parties to ensure that the VR runtimes have prefixes in the resource paths that they access to allow wildcards to work effectively when the runtimes are updated by end users. If its not possible to ensure forward compatibility with these rules, we will need to either have limited sandboxing on the VR process or implement a mechanism to update the sandbox rules for the VR process in release builds. (The sandboxing rules are currently hard-coded)
Reporter | ||
Comment 1•7 years ago
|
||
Please see comments in Bug 1359460 for details of the initial exploration of the sandbox rules required for OpenVR and Oculus runtimes.
See Also: → 1359460
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•