Taking a break from whitelisting/sandboxing and malicous users.
R
There are 1281 functions in the base package version 3.4.4.
As mentioned in Part 1, I’m looking into the idea of running R code which may originate from potentially malicious sources e.g. code from a web interface, or a database or even a tweet!
I’m looking into the idea of running R code which may originate from potentially malicious sources e.g. code from a web interface, or a database or even a tweet!
As described in a prior post I need to save some configuration objects from R into human-readable, human-editable format.
