59 bytes, text/x-review-board-request
Using sandbox_init_with_parameters with save us from some of the slightly messy interpolation. It does not appear to be documented (but then, basically none of the sandbox infrastructure is!), however both Chrome and WebKit appear to use it, so I think it's safe.
Attachment #8854077 - Flags: review?(haftandilian)
Comment on attachment 8854077 [details] Bug 1353040 - Switch from sandbox_init to sandbox_init_with_parameters https://reviewboard.mozilla.org/r/126060/#review128668 r+ For the approach because named parameters are less error prone. Please add some support to make printing the policy for debugging straightforward. I think printing the params vector followed by the policy would be sufficient. No need to do string interpolation. And then re-request review. Thanks. Once concern I mentioned on IRC was that with sandbox_init_with_parameters, we don't get to see the final policy string before passing it of to the OS. i.e., we don't get to see exactly how the argument strings are interpolated into the policy.
Attachment #8854077 - Flags: review?(haftandilian) → review+
Comment on attachment 8854077 [details] Bug 1353040 - Switch from sandbox_init to sandbox_init_with_parameters https://reviewboard.mozilla.org/r/126060/#review128996
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/07cf34197c32 Switch from sandbox_init to sandbox_init_with_parameters. r=haik
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox55: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.