On Thu, Apr 21, 2016 at 5:53 PM, Jason Orendorff <[email protected]> wrote:
> On Thu, Apr 21, 2016 at 4:00 PM, Bobby Holley <[email protected]> > wrote: > > Note that a while back I added a mechanism where you can easily ban > script from ever running again in a compartment - see [1] for a usage > example. > > > > So this should be a trivial (and probably worthwhile) patch. > > Agreed! > > Separately from that possible patch: there's a similar mechanism inside > the engine, which also stops JS execution on a per-compartment basis, > though along a different boundary. I think Shu added it, and quite > recently. The Debugger uses it so that poking around in the debugger can't > accidentally run debuggee code. Should we unify the two things? > Most likely yes. The XPConnect version prevents the browser from calling into the engine to execute script (modulo bugs). It should probably activate the engine-internal mechanism as well. > > -j > > _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
