What a one line change did to the Chrome sandbox

Re:What a one line change did to the Chrome sandbox by ChrisSD on Thursday April 23, 2020 @04:59AM (#22954070)

> The Chromium sandbox on Windows has stood the test of time. It’s considered one of the better sandboxing mechanisms deployed at scale without requiring elevated privileges to function.

For anyone who is interested in the history, this type of Restricted Token & Job Object sandbox was, as far as I know, first used in MOICE (Microsoft Office Isolated Conversion Environment). This was created by Microsoft's Office Trustworthy Computing group to isolate the conversion of `.doc` to `.docx`. David LeBlanc blogged about it in 2007, with his "Practical Windows Sandboxing" series[0][1][2]. Of course a third party may have independently discovered the same techniques but kept it to themselves.

The state of the art has improved since then but the general principles are the same.

[0]: https://docs.microsoft.com/en-us/archive/blogs/david_leblanc...

[1]: https://docs.microsoft.com/en-us/archive/blogs/david_leblanc...

[2]: https://docs.microsoft.com/en-us/archive/blogs/david_leblanc...

[ Parent | on HN ]

Re:What a one line change did to the Chrome sandbox by bits_of_bytes on Thursday April 23, 2020 @12:47PM (#22957956)

I believe some chromium sandbox logic came from GreenBorder (https://en.m.wikipedia.org/wiki/GreenBorder) but I don't know the timeline of that or how GreenBorder sandboxing was implemented.

[ Parent | on HN ]

Re:What a one line change did to the Chrome sandbox by signal11 on Thursday April 23, 2020 @10:02AM (#22956067)

Are there any antivirus vendors which now use these techniques? I know there was a spat between a member of the Chrome team and antivirus vendors about the latter not using sandboxes.

[ Parent | on HN ]