3 ms·

In the end you're getting full fledged binary which can run anything on your system. Also I'm not sure if sandboxing on Windows even exists.

pas 4y ago
it does, Chrome and Firefox uses it https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox.md#sandbox-restrictions https://chromium.googlesource.com/chromium/src/+/HEAD/docs/d... it's not as simple as unshare() for namespaces on Linux, but works pretty well
- HAL9000Ti 4y ago
  This is a chromium feature, not a windows one.
  - skissane 4y ago
    > This is a chromium feature, not a windows one. Chromium's sandbox on Windows is built on top of Windows features (tokens, jobs, desktops, integrity levels, app containers) Just like how their sandbox on Linux is built on top of Linux features (setuid, user namespaces, seccomp, SELinux, AppArmor) For both Linux and Windows, the OS kernel gives you a bunch of features you can use to construct sandboxes, but the choice of exactly which of those features you use, and how you put them together, is up to you. Chromium worked out how to combine those features to meet their own security requirements, and has documented that in detail, and open sourced the implementation – there's nothing stopping you from copying the same approach, assuming your requirements are sufficiently similar With macOS, Apple ships a sandboxing mechanism in the OS, known as "sandbox" or "seatbelt", which is what Chromium uses there
wongarsu 4y ago
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 https://github.com/sandboxie-plus/Sandboxie 2: https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-sandbox/windows-sandbox-overview https://learn.microsoft.com/en-us/windows/security/threat-pr... 2b: https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-sandbox/windows-sandbox-architecture https://learn.microsoft.com/en-us/windows/security/threat-pr...

pas 4y ago

it does, Chrome and Firefox uses it https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox.md#sandbox-restrictions https://chromium.googlesource.com/chromium/src/+/HEAD/docs/d... it's not as simple as unshare() for namespaces on Linux, but works pretty well

HAL9000Ti 4y ago
This is a chromium feature, not a windows one.
- skissane 4y ago
  > This is a chromium feature, not a windows one. Chromium's sandbox on Windows is built on top of Windows features (tokens, jobs, desktops, integrity levels, app containers) Just like how their sandbox on Linux is built on top of Linux features (setuid, user namespaces, seccomp, SELinux, AppArmor) For both Linux and Windows, the OS kernel gives you a bunch of features you can use to construct sandboxes, but the choice of exactly which of those features you use, and how you put them together, is up to you. Chromium worked out how to combine those features to meet their own security requirements, and has documented that in detail, and open sourced the implementation – there's nothing stopping you from copying the same approach, assuming your requirements are sufficiently similar With macOS, Apple ships a sandboxing mechanism in the OS, known as "sandbox" or "seatbelt", which is what Chromium uses there

wongarsu 4y ago

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 https://github.com/sandboxie-plus/Sandboxie 2: https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-sandbox/windows-sandbox-overview https://learn.microsoft.com/en-us/windows/security/threat-pr... 2b: https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-sandbox/windows-sandbox-architecture https://learn.microsoft.com/en-us/windows/security/threat-pr...