News for hackers. Stuff that matters.

A comment on Binctr: Static, unprivileged, self-contained containers as executable binaries. Parent comment

Re:Binctr: Static, unprivileged, self-contained containers a... by GordonS on Sunday December 23, 2018 @07:52AM (#18745805)
Interestingly, there was a post in HN recently about the next build of Windows introducing sandboxing. It really feels like there has been a steady stream of new security features coming out of Microsoft lately, which is great to see.
[ Parent | on HN ]
Re:Binctr: Static, unprivileged, self-contained containers a... by walterbell on Sunday December 23, 2018 @08:05AM (#18745851)
The upcoming Microsoft capability appears to be inspired by Bromium, https://www.pcworld.com/article/3169668/browsers/hp-hardens-..., which has long provided "seamless ephermal virtualization" on Win 7/10.
[ Parent | on HN ]
Re:Binctr: Static, unprivileged, self-contained containers a... by saagarjha on Sunday December 23, 2018 @09:54AM (#18746361)
Of course, this “sandboxing” is the equivalent of running apps in a CoW virtual machine.
[ Parent | on HN ]
Re:Binctr: Static, unprivileged, self-contained containers a... by nijave on Sunday December 23, 2018 @10:21AM (#18746535)
The sandbox can share memory with the host but says it is running a separate kernel https://techcommunity.microsoft.com/t5/Windows-Kernel-Intern...

I think just saying it's a VM is an over simplification

[ Parent | on HN ]
Re:Binctr: Static, unprivileged, self-contained containers a... by saagarjha on Sunday December 23, 2018 @08:24PM (#18749626)
That’s what I said, though. It will copy-on-write memory pages and files.
[ Parent | on HN ]