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-03-03 18:51:17 -08:00
2014-03-04 12:25:59 -08:00
2014-03-04 12:26:50 -08:00
2014-02-27 13:35:00 -08:00
2014-03-04 17:26:52 -08:00
2014-03-04 10:19:20 -08:00
2013-08-14 14:05:35 -07:00
2014-03-05 22:14:25 +08:00
2014-02-24 17:38:49 -08:00

Atom — The hackable editor

Atom

Check out our guides and API documentation.

Installing

Download the latest Atom release.

Atom will automatically update when a new release is available.

Building

Follow the instructions in the build docs.

Description
No description provided
Readme 447 MiB
Languages
JavaScript 88.3%
Less 8.7%
CoffeeScript 2.8%
Shell 0.1%