Release v1.14.3 / 5.69.3

[DavidXanatos]

In the 1.14.x release line, several significant updates and fixes have been introduced to enhance the functionality and performance of sandboxed processes. These enhancements are aimed at providing users with a more robust and versatile experience, ensuring smoother and more secure operations.

One of the major updates is the introduction of the ability to force sandboxed processes to use a predefined SOCKS5 proxy. This feature allows for more controlled and secure network interactions. Additionally, the capability to intercept DNS queries for logging or redirection has been added, providing administrators with greater oversight and flexibility in managing network traffic. Notably, support for SOCKS5 proxy authentication based on RFC1928 has been incorporated, thanks to Deezzir's contributions, who also developed a Test Dialog UI for the SOCKS5 proxy. It is important to note that utilizing the Proxy and DNS features requires an advanced type certificate.

The release also introduces a new command line option, /fcp /force_children, to the start.exe utility. This option enables the initiation of a program outside the sandbox while ensuring that all its child processes are sandboxed, enhancing security without compromising flexibility. Additionally, a new feature allows for the limitation of memory usage and the number of processes within a single sandbox through job objects. This was made possible by Yeyixiao's contribution and can be configured using "TotalMemoryLimit" for overall sandbox memory limits and "ProcessMemoryLimit" for individual process limits.

Further improvements include the addition of a new "Sandboxie\All Sandboxes" SID to the token creation process, which fundamentally alters the token creation mechanism. This feature can be activated with the "SandboxieAllGroup=y" setting. Users can now also configure the "EditAdminOnly=y" setting on a per-box basis, providing more granular control over administrative permissions. Additionally, a new UI option allows users to start unsandboxed processes while forcing child processes into a sandbox, and the "AlertBeforeStart" option prompts a warning before launching a new program into the sandbox if the initiating program is not a Sandboxie component.

Moreover, the update introduces a mechanism to block unsafe calls via RPC Port message filtering and a template to prevent sandboxed processes from accessing system information through WMI. A new "Job Object" Options page has been added, consolidating all job object-related options for easier management. Several critical fixes have been implemented, including resolving Chrome printing problems and various bugs affecting sandbox properties and program launching. Compatibility with Steam running sandboxed has also been improved.

Compatibility with Windows build 26217 has been validated, and dynamic data has been updated accordingly. Finally, an issue with an early batch of Large Supporter certificates has been resolved, ensuring smoother operation and fewer disruptions. These updates collectively enhance the security, performance, and usability of sandboxed processes, providing users with a more reliable and efficient environment.

For a full list of changes and fixes please review the full change log.

You can support the project through donations, any help will be greatly appreciated.

If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new build.

---

This discussion was created from the release Release v1.14.3 / 5.69.3.

[KT907]

Broke Shadowsocks. Does not proxy in the sandbox. Version 5.69.3. The previous release does not have this problem. Does this have anything to do with the innovations with proxies?

P.S The proxy also stopped working in the FreeTube program.

[e-t-l]

Did "EditAdminOnly=y" get applied to everything by default if Admin restrictions weren't already set? After updating SBIE+, any time I try to edit a sandbox I get an error about admin privileges, and I need to relaunch Sandboxie as Admin. I did not have to do that before, which means that previously, either 1) Sandboxie was not requiring admin permission at all, or 2) Sandboxie was launching as administrator automatically at boot.

I do currently have Sandboxie set to start automatically at boot; is there a way to make it start automatically elevated? (I guess I could make a scheduled task to launch it elevated at login, but given that this behavior is new to this version of Sandboxie, I wanted to check if there was a native way to do it first)