We are excited to announce the latest updates to Sandboxie Plus 1.15.3, these updates introduce impactful new features, significant improvements, and critical fixes to enhance user experience, customization, and security. For enhanced security, this release includes a mechanism to restrict access to sandbox folders to the user who created them. Users can also choose to retain or modify Access Control Lists (ACLs) on sandboxed files, providing more flexibility in access management, though this may introduce compatibility issues in some cases. Importantly, this update addresses a security vulnerability documented under CVE-2024-49360. This release also includes the introduction of a user proxy mechanism, enabling user-specific operations, along with support for the Encrypting File System (EFS). By adding the configuration EnableEFS=y to sandbox settings, users can now utilize EFS within the sandbox environment. The new OpenWPADEndpoint=y option allows access to system proxy configuration, expanding sandbox functionality. Additionally, trace logging filtering has been enhanced, and by enabling LogMessageEvents in global settings, all Sandboxie events can now be logged directly to the Windows Event Log for better tracking and analysis. Technical improvements in this release include refinements to the startup processes for SandboxieCrypto, ensuring smoother operations. Applications launched via drag-and-drop now consistently use their parent folder as the working directory, improving user experience. Compatibility with Windows build 27749 has been validated to ensure a seamless experience for users. Additionally, crashes affecting Firefox Nightly have been resolved, ensuring better browser compatibility. We thank our contributors and users for their invaluable feedback and support. Update now to take advantage of the latest features, enhancements, and security improvements in Sandboxie Plus. Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.3 Added improved ini section editor, it now supports search Ctrl+F added SBIE1321 to log all force process events, can be enabled with "NotifyForceProcessEnabled=y", Improves #4113 Changed improved support notification Fixed fixed issues with SSL on ARM64 platform, breaking updater and cert retrieval
Running well on my Win7x64 (in portable mode) I guess the [issue](https://www.wilderssecurity.com/threads/sandboxie-plus-1-15-2.455497/#post-3216172) of Run Outside Sandbox from Context Menu not working re-posted on github as [#4403](https://github.com/sandboxie-plus/Sandboxie/issues/4403) did not get fixed in time for this release.
David, I've noticed an odd issue with an email notifier I use called PopPeeper. I use the SBIE classic version 5.70.3. When I run this program unsandboxed it works fine. If I force it to run in the sandbox it chokes on the logging into Gmail phase. I use Oauth2 ilo regular password access. Nothing has changed anywhere else except for a SBIE update. I'm not 100% sure this is a sandbox issue but I am running out of options to try. Any thoughts? Thanks. ETA: I reverted to an older version of the classic, 5.70.0 and everything works fine with that one. I was also getting odd errors when I started chrome sandboxed with the latest version. ETA: here is the Chrome error, it will not start now.
Hi folks, I have got an issue that I am pretty sure caused by operator oversight. If anyone can give a pointer I would appreciate. Case: Firefox vs MS Edge - Ok - both <red> password protected-enhanced privacy, encrypted sandboxes. On Firefox, recently when I download files that are approx 1/3 Gb or larger I get an error saying there is not enough room on the disc and downloads fail. On MS Edge, same box structure but I can download away many gigs at a time with no problems. It took so long to setup these boxes to my liking, I am lazy and have just started using Edge more but I really want to stay with Firefox sandboxed. Any thoughts or tips?
Thanks for the reply David. It actually started doing it with 5.70.3 also so I reverted all the way back to 5.69.6 and it works so far. This could be on Google and their Oauth2 servers. The error seems to come and go oddly so I don't think I'll be able to pinpoint it for you. The browsers errors - I don't know. They are gone now. When I forced PopPeeper to run sandboxed, it seemed to choke on the Oauth2 sign in. When I removed the forced setting and ran it sandboxed using the "run any program sandboxed" option it seemed to work. It always worked non sandboxed. I do have both Chrome and PopPeeper in my restriction list so it's possible something else was trying to run and could not, though I did not get any errors. Can you help me understand - what are the changes that happen to the classic version with all the updates to the plus? Maybe I should stop updating the Classic when the Plus updates? Appreciate the help here.
BTW, does this new version work with Windows 8.1? I would like to sandbox multiple versions of Firefox, so that I can run them side by side on a friend's system. I stopped using a sandboxed Firefox years ago, because eventually it would make Firefox use 100% of the CPU, did you guys ever see this problem when combining Firefox with Sandboxie? And I assume in order to fully separate them, I should uncheck the ''give full access to firefox profile folder'' setting, right?
Not me. Never. To have different versions of Firefox at the same time, you need to install each version in a separate sandbox and set up each sandbox with the settings below. After installing each version in its own sandbox, before restarting the browser, make sure to put a distribution folder with the policies.json file inside that disables automatic updates for Firefox. I won't go in details about this because I know you know about it. I think you said before that this method for disabling automatic updates dont work for you. It should work. If you set it up right, it works. If you dont do this, you gonna have Firefox trying to auto update. I never had more that 2 Firerfox versions at the same time but you should be able to install 3 or 4 or 5, as many as you want. Bo
Thanks for the help Bo, and good to see you. But I'm afraid I have some bad news, once again Firefox started to use 100%, keep in mind this is the newest Firefox version for Win 8.1, freshly installed inside the sandbox. However, I was using an old version of Sandboxie, because I don't know if newer versions will work on Win 8.1, but I guess I should try. And about auto updating, this can indeed be stopped, but what can't be stopped is the annoying update pop up. I have noticed that even if you block Firefox from making outbound connections, it will still pop up, so this is clearly baked in. But I did notice something about Firefox, regarding the ability to run multiple versions side by side, I will explain it in the Firefox topic. This would mean that I don't even need Sandboxie, for this purpose.
Thanks and wow, I'm surprised that Sandboxie still supports Win 8.1, I wonder how David Xanatos managed to achieve this?
This high CPU you experience has to be something else other than SBIE and Firefox. Probably a security program in the mix that you have is triggering the 100% cpu usage, caused when it detects activity in the sandbox. The mentioned method to block Firefox from updating works silently. I have never seen a pop up or message due to blocking Firefox from auto updating. Also, I have never changed a setting in the firewall due to blocking Firefox updates. In fact, I have never changed anything in the firewall for any reason in W10. Bo
Look at this... https://youtu.be/8MnRy2RQaTg Fan Control is not running on top of Sandboxie. Portable Catsxp is the default browser and is forced.
No issues to report here. I thought there might've been another issue with freetube, turns out that was an issue with invidious caused by youtube.
