Open
Bug 1014407
Opened 10 years ago
Updated 2 years ago
Failure when setting stdout or stderr on the Windows process sandboxing policy should be reported as a warning.
Categories
(Core :: Security: Process Sandboxing, defect)
Tracking
()
NEW
People
(Reporter: bobowen, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: sb+)
Once we have the logging worked out for the Chromium sandbox code, we should log a warning if we are unable to set the stdout and stderr on the policy.
|
||
Comment 1•9 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•8 years ago
|
Whiteboard: sb+
|
Reporter | |
Updated•8 years ago
|
Flags: needinfo?(bobowen.code)
|
|
Reporter | |
Comment 2•8 years ago
|
||
I remember now this depends on getting some logging in the chromium sandbox working. Either that or if SandboxBroker is moved into xul.
Depends on: 1055227
Flags: needinfo?(bobowen.code)
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•