warriordog / acomputerbot Goto Github PK

I cheated when writing the JS security manager by having it check if the call originated in the JSExecutor class, and if so verify that it was a whitelisted permission. However this opens the door for a compromised JS environment to be able to perform any of the whitelisted actions, including reflection and classloaders (why does something built into java need that?). This will also replace the long process of scanning the stack trace with a single check.

scattered around the code are various forms of the same method that does things like split a multi-line string into different messages, or remove newlines from a string. These need to be merged into StringCheck.

Currently log IO has not caused a performance issue, but when logging lots of commands having a separate thread would speed things up a lot.

Replace "/logs/..txt" with "/logs//.txt" to better organize log files.