Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Sandboxie
Sandboxie+ Release v1.0.17 / 5.55.17
Message
<blockquote data-quote="bjm_" data-source="post: 982022" data-attributes="member: 36475"><p>Sandboxie+ Release v1.0.16 / 5.55.16</p><p>[plain]https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.16[/plain]</p><p><strong>Note: Pre-release</strong></p><p><strong></strong></p><p><strong>This build fixes a couple of issues, but also introduces a major change in how sandboxie controls access to process memory.</strong></p><p></p><p>Before this build sandboxie allowed sandboxed programs to read the memory of any unsandboxed program belonging to the current user, this is obviously a bad idea if your goals is not only infection prevention but also data protection. Hence with 1.0.16 onwards sandboxie will not allow for PROCESS_VM_READ on unsandboxed processes or processes belonging to other boxes.</p><p>To facilitate compatibility this build introduces a IPC options, with ReadIpcPath=$program.exe any unboxed process can be configured to allow for PROCESS_VM_READ, it is also possible to restore the old behavior entirely by specifying ReadIpcPath=$:*</p><p>By default the only process whos memory can be read is explorer.exe many processes want that and explorer should not keep any secrets normally anyways. To block this you can use ClosedIpcPath=$:explorer.exe</p><p></p><p>To facilitate optimal process isoaltion the EnableObjectFiltering option is now on by default, although this only applies for new installations, hence its recommend for existing installation to go to settings->advanced and enable it explicitly.</p><p></p><p>Other changes in this build include a simple resource access monitor mode and a change how process paths are resolved for sandboxed processes, this should fix a couple of issues.</p><p></p><p><strong>Given that this build changes a couple of core mechanics it is possible that in some special cases this can lead to an incompatibility.</strong></p><p></p><p>If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new build.</p><p>You can support the project through donations, any help will be greatly appreciated.</p><p></p><p>[URL unfurl="true"]https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.16[/URL]</p></blockquote><p></p>
[QUOTE="bjm_, post: 982022, member: 36475"] Sandboxie+ Release v1.0.16 / 5.55.16 [plain]https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.16[/plain] [B]Note: Pre-release This build fixes a couple of issues, but also introduces a major change in how sandboxie controls access to process memory.[/B] Before this build sandboxie allowed sandboxed programs to read the memory of any unsandboxed program belonging to the current user, this is obviously a bad idea if your goals is not only infection prevention but also data protection. Hence with 1.0.16 onwards sandboxie will not allow for PROCESS_VM_READ on unsandboxed processes or processes belonging to other boxes. To facilitate compatibility this build introduces a IPC options, with ReadIpcPath=$program.exe any unboxed process can be configured to allow for PROCESS_VM_READ, it is also possible to restore the old behavior entirely by specifying ReadIpcPath=$:* By default the only process whos memory can be read is explorer.exe many processes want that and explorer should not keep any secrets normally anyways. To block this you can use ClosedIpcPath=$:explorer.exe To facilitate optimal process isoaltion the EnableObjectFiltering option is now on by default, although this only applies for new installations, hence its recommend for existing installation to go to settings->advanced and enable it explicitly. Other changes in this build include a simple resource access monitor mode and a change how process paths are resolved for sandboxed processes, this should fix a couple of issues. [B]Given that this build changes a couple of core mechanics it is possible that in some special cases this can lead to an incompatibility.[/B] If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new build. You can support the project through donations, any help will be greatly appreciated. [URL unfurl="true"]https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.16[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top
