Files
atom/static
Nathan Sobo 5e8213d45f Add atom.allowUnsafeEval loophole and disable unsafe-eval again
With Node.js baked in, there's no water-tight way to prevent users from
evaluating code at runtime, at least with CSP alone. This is because
node exposes a 'vm' module that allows scripts to be compiled. There's
also `module._compile`, etc.

I think a reasonable compromise is to protect users from eval'ing code
by accident. This commit adds an atom.allowUnsafeEval method which
re-enables eval in the dynamic scope of the given function.

I then use this to compile the keystroke grammar which saves us the
complexity of pre-compiling it during specs.

What do people think?
2014-03-05 09:57:08 -07:00
..
2014-02-28 17:38:08 -08:00
2013-12-06 12:56:14 -08:00
2013-09-20 18:03:21 -07:00
2013-09-10 12:01:16 -07:00
2014-02-11 16:19:46 -08:00
2013-09-12 14:04:17 -07:00
2013-06-12 13:28:39 -07:00
2013-03-11 10:02:18 -07:00
2014-01-29 18:00:00 -08:00
2014-01-29 18:00:00 -08:00
2013-12-03 10:37:31 -08:00
2013-09-10 11:59:39 -07:00
2013-09-12 14:04:18 -07:00
2013-09-26 15:37:28 -07:00
2013-12-06 12:56:14 -08:00
2013-10-23 10:42:13 -07:00