In this release:
- Isolation of windows and window classes on the desktop prevents sandboxed programs from discovering an already-running unsandboxed instance of themselves. For example, a new sandboxed Firefox window will not discover and join an already-running non-sandboxed Firefox process.
- Sandboxie Control adds a new action to run any program under the supervision of Sandboxie.
- Opening or exploring a folder from a sandboxed process will open the folder in a sandboxed window of Internet Explorer, rather than an unsandboxed of the Windows Explorer. This provides more consistent behavior for sandboxed programs, at the small cost of requiring Internet Explorer to be installed (which should be the case on most systems anyway).
- Sandboxie will fail access to mailto: links (at least under Internet Explorer), because opening the mail client inside the sandbox (and potentially saving some messages in the sandbox) is probably not what the user intended.
- Sandboxed processes are denied access to the Service Control Manager. This means better protection, but, at least as of this release, also means that Windows Installer-based installers will not work within the sandbox.
- The Working In Background cursor no longer appears when the browser is launched.
- Fixed a bug that causes more registry keys to be created in the sandbox than necessary.
- Sandboxie Control now deletes the registry keys in the sandbox, in addition to deleting disk files, when it empties the sandbox.
- Sandboxie Toolbar, when used outside the sandbox, warns that navigating to a sandboxed favorite does not mean the browser becomes sandboxed itself.
- On system startup, Sandboxie Control waits longer for the system initialization to complete, before announcing it cannot connect to the kernel mode driver.
Straight from the horse's mouth
1 post • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest