Closed
Bug 1102215
Opened 10 years ago
Closed 10 years ago
Move security/sandbox/chromium/base/shim/ to new directory security/sandbox/chromium-shim/
Categories
(Core :: Security: Process Sandboxing, defect)
Core
Security: Process Sandboxing
Tracking
()
RESOLVED
FIXED
mozilla38
People
(Reporter: bobowen, Assigned: bobowen)
References
Details
Attachments
(1 file)
Move security/sandbox/chromium/base/shim/ to new directory security/sandbox/chromium-shim/
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → bobowencode
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•10 years ago
|
||
As well as moving the shim code to its own separate directory, I've also moved the sandbox logging code into the new shim directory.
This is required to compile the chromium code because of the small changes we've made, so I think the shim directory is the most sensible place for it to live.
I've also moved the SDK declarations header into the base/win directory within the shim as it is windows specific.
Attachment #8534877 -
Flags: review?(ted)
Comment 3•10 years ago
|
||
Move process sandboxing bugs to their new, separate component.
(Sorry for the bugspam; filter on 3c21328c-8cfb-4819-9d88-f6e965067350.)
Component: Security → Security: Process Sandboxing
Updated•10 years ago
|
Attachment #8534877 -
Flags: review?(ted) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Comment 5•10 years ago
|
||
sorry had to back this in https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=60b4850423d3 out for bustage like:
https://treeherder.mozilla.org/logviewer.html#?job_id=5759810&repo=mozilla-inbound
Assignee | ||
Comment 6•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•