Closed
Bug 1102197
Opened 10 years ago
Closed 10 years ago
[Tracker] Move all of the Chromium sandboxing code into the same structure as the Chromium repository.
Categories
(Core :: Security: Process Sandboxing, defect)
Core
Security: Process Sandboxing
Tracking
()
RESOLVED
FIXED
People
(Reporter: bobowen, Unassigned)
References
Details
(Keywords: meta)
Currently we have the following directories that contain Chromium sandboxing code:
security/sandbox/build/
security/sandbox/chromium/
security/sandbox/linux/
security/sandbox/win/
Apart from build, these all also contain non-Chromium code.
To aid future merging it would be good to move all of the Chromium code into security/sandbox/chromium/ and the shim code that exists in security/sandbox/chromium/base/shim/ into a separate directory under security/sandbox/
|
||
Comment 1•10 years ago
|
||
Move process sandboxing bugs to the new Bugzilla component.
(Sorry for the bugspam; filter on 3c21328c-8cfb-4819-9d88-f6e965067350.)
Component: Security → Security: Process Sandboxing
|
Reporter | |
Comment 2•10 years ago
|
||
All blocking bugs fixed.
All of our copied sandboxing Chromium code now sits in security/sandbox/chromium/ and the directory structure matches Chromium's.
There are some minor changes tracked in:
security/sandbox/modifications-to-chromium-to-reapply-after-upstream-merge.txt
and the Chromium commit of directories or files is recorded in:
security/sandbox/moz-chromium-commit-status.txt
The shim code needed to compile the Chromium code is now in:
security/sandbox/chromium-shim/
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•