community VS Sandboxie

A list of adopters (many of which are hosting providers) is here: https://github.com/buildpacks/community/blob/main/ADOPTERS.m...

Many comments here point out how difficult it is to manage a separate dependency stack for each container when you use Dockerfiles to build them. This problem is just as difficult, time-intensive, and security-critical for microservice apps running on K8s as it is for CLI tools and graphical apps.

Worth pointing out that there is an incubating CNCF project that tries to solve this problem by forgoing Dockerfiles entirely: Cloud Native Buildpacks (https://buildpacks.io)

CNB defines safe seams between OCI image layers so that can be replaced out of order, directly on any Docker registry (only JSON requests), and en-mass. This means you can, e.g., instantly update all of your OS packages for your 1000+ containers without running any builds, as long as you use an LTS distribution with strong ABI promises (e.g., Ubuntu 20.04). Most major cloud vendors have quietly adopted it, especially for function builds: https://github.com/buildpacks/community/blob/main/ADOPTERS.m...

You might recognize "buildpacks" from Heroku, and in fact the project was started several years ago in the CNCF by the folks who maintained the Heroku and Cloud Foundry buildpacks in the pre-Dockerfile era.

[Disclaimer: I'm one of the founders of the project, on the VMware (formerly Cloud Foundry) side.]

I used to use sandboxie so I could emulate multiple browser sessions without worrying about cached creds or the different portals screwing up my context. It works decently.

Use Sandboxie on Windows. It's open source these days, and isolates processes from making changes on your system. It's perfect to install and run potentially unsafe programs. Sandboxie exists since 2003, and yet we still have people in business worlds running viruses from mail attachments.

Sandboxie

You can allow applications inside a Sandboxie to communicate with each other through sockets even when network access by Sandboxie is blocked1. You can enable Sandboxie network access and use Windows firewall outside Sandboxie to block all applications inside the Sandboxie from accessing the network1. It is also possible to specify ports that cannot be accessed by boxed applications2. However, it is not possible to specify IP’s or IP ranges that cannot be accessed by boxed applications2.

In addition to just taking all privileges way from the process, like Chrome does, there's also Sandboxie [1] and the official Windows Sandbox [2]

1: https://github.com/sandboxie-plus/Sandboxie

2: https://learn.microsoft.com/en-us/windows/security/threat-pr...

2b: https://learn.microsoft.com/en-us/windows/security/threat-pr...

VirtualBox dropped 3D acceleration for old OS like XP a while back, you can see it it running "dxdiag" on your windows XP and running the tests, it will do DirectDraw only since the game is a 32 bit windows game it should run on modern windows like 10 and 11, I saw that the main problem is the DRM, so you will need a "cracked/pached" exe, I can't help with that, but do your own search, if you want to be "safe" you can try running it using something like SandBoxie-plus https://github.com/sandboxie-plus/Sandboxie/releases

With those pre-reqs, is there anything Windows Sandbox can do that Sandboxie can't?

https://github.com/sandboxie-plus/Sandboxie

Could you pls. test if the vulnerability can be mitigated by using Sandboxie-Classic (that is the free version)?

I also want to recommand this piece of small software but it's very neat, Sandboxie: https://github.com/sandboxie-plus/Sandboxie