jiti-meet/react/features/base/lib-jitsi-meet
Saúl Ibarra Corretgé 4a8f787519 rn: evaluate config.js in a sandboxed environment
We are downloading code off the Internet and executing it on the user's device,
so run it sandboxed to avoid potential bad actors.

Since it's impossible to eval() safely in JS and React Native doesn't offer
something akin to Node's vm module, here we are rolling our own.

On Android it uses the Duktape JavaScript engine and on iOS the builtin
JavaScriptCore engine. The extra JS engine is *only* used for evaluating the
downloaded code and returning a JSON string which is then passed back to RN.
2019-10-14 12:20:58 +02:00
..
native logging: use individual, names loggers 2019-08-23 10:57:38 +02:00
_.native.js ref(strophe): Remove and cleanup all strophe related code. 2017-10-23 16:27:30 -05:00
_.web.js cleanup: drop polyfills which were required for IE11 2018-07-11 17:53:32 +02:00
actionTypes.js chore: use strings as action types 2019-03-21 14:47:55 +01:00
actions.js flow: tame the beast 2019-03-21 14:47:55 +01:00
functions.any.js rn: evaluate config.js in a sandboxed environment 2019-10-14 12:20:58 +02:00
functions.native.js rn: evaluate config.js in a sandboxed environment 2019-10-14 12:20:58 +02:00
functions.web.js rn: evaluate config.js in a sandboxed environment 2019-10-14 12:20:58 +02:00
index.js feat: Displays the E2E RTT in the connection stats table. (#3344) 2018-08-07 11:31:51 -07:00
logger.js logging: use individual, names loggers 2019-08-23 10:57:38 +02:00
middleware.js core: refactor routing 2018-07-11 22:58:41 -05:00
reducer.js core: refactor routing 2018-07-11 22:58:41 -05:00