News for hackers. Stuff that matters.
Re:Microsoft didn’t sandbox Windows Defender, so I did by adzm on Wednesday August 02, 2017 @03:33PM (#14913843)
implemented in JavaScript... something like this?

https://bugs.chromium.org/p/project-zero/issues/detail?id=12...

> The core component of MsMpEng responsible for scanning and analysis is called mpengine. Mpengine is a vast and complex attack surface, comprising of handlers for dozens of esoteric archive formats, executable packers and cryptors, full system emulators and interpreters for various architectures and languages, and so on. All of this code is accessible to remote attackers.

> NScript is the component of mpengine that evaluates any filesystem or network activity that looks like JavaScript. To be clear, this is an unsandboxed and highly privileged JavaScript interpreter that is used to evaluate untrusted code, by default on all modern Windows systems. This is as surprising as it sounds.

Re:Microsoft didn’t sandbox Windows Defender, so I did by digi_owl on Wednesday August 02, 2017 @05:06PM (#14914651)
Time we bring back the C64 design, with no internal storage?
Re:Microsoft didn’t sandbox Windows Defender, so I did by syrrim on Wednesday August 02, 2017 @08:04PM (#14915842)
And no networking.
Re:Microsoft didn’t sandbox Windows Defender, so I did by retox on Thursday August 03, 2017 @04:36AM (#14917932)
Try TempleOS, though a scamp from /g/ implemented a full network stack, along with video players, etc.
Re:Microsoft didn’t sandbox Windows Defender, so I did by digi_owl on Thursday August 03, 2017 @12:20PM (#14920932)
And thus the first shim was formed...