Move security/sandbox/chromium/base/shim/ to new directory security/sandbox/chromium-shim/

RESOLVED FIXED in mozilla38

Status

()

defect
RESOLVED FIXED
5 years ago
2 years ago

People

(Reporter: bobowen, Assigned: bobowen)

Tracking

unspecified
mozilla38
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Assignee

Description

5 years ago
Move security/sandbox/chromium/base/shim/ to new directory security/sandbox/chromium-shim/
Assignee

Updated

5 years ago
Assignee: nobody → bobowencode
Status: NEW → ASSIGNED
Assignee

Updated

5 years ago
Blocks: 1102213
Assignee

Comment 2

5 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)
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
Attachment #8534877 - Flags: review?(ted) → review+
https://hg.mozilla.org/mozilla-central/rev/aace33119067
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Depends on: 1376652
Blocks: 1376652
No longer depends on: 1376652
You need to log in before you can comment on or make changes to this bug.