By the way, more information is available here: https://wiki.mozilla.org/Security/Sandbox/Seccomp <https://wiki.mozilla.org/Security/Sandbox/Seccomp> https://wiki.mozilla.org/Security/Sandbox <https://wiki.mozilla.org/Security/Sandbox>
Note especially [1] as that will tell you if you hit any issues with seccomp enabled. [1] https://wiki.mozilla.org/Security/Sandbox/Seccomp#Seccomp_reporter > On 2 Nov 2015, at 9:32 am, Michael Wu <[email protected]> wrote: > > Enable it in the kernel. It's a required part of the platform. It lets us > specify what syscalls are allowed to be called in child processes. Backports > are available. https://bug790923.bmoattachments.org/attachment.cgi?id=8421852 > <https://bug790923.bmoattachments.org/attachment.cgi?id=8421852> > > -Michael Wu > > On Sun, Nov 1, 2015 at 3:06 AM, Adam Farden <[email protected] > <mailto:[email protected]>> wrote: > Hi, > > I recently ported LG G3 to fxos using CyanogenMod repos. When enabling > SECCOMP in the kernel I found that SECCOMP_FILTER is not present in this > device's kernel. > > I quickly worked around this by compiling gecko with: > > ac_add_options --disable-content-sandbox > ac_add_options --disable-sandbox > > but what are the consequences of this? The OS appears to run correctly under > the limited testing I did. > > Adam > > _______________________________________________ > dev-fxos mailing list > [email protected] <mailto:[email protected]> > https://lists.mozilla.org/listinfo/dev-fxos > <https://lists.mozilla.org/listinfo/dev-fxos> > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
