[.01] Changes to OpenWinClass=*
Posted: Tue Jun 25, 2013 5:34 am
As you may know, in version 4, the process in the sandbox is confined into a "job" concept which prevents interacting with window objects outside the sandbox.
This has two major implications:
- All interactions with window objects outside the sandbox have to go through a SbieSvc proxy process.
- Lower level requests such as simulating keyboard input, registering a hotkey or changing system parameters are not supported.
Version 4.03 revises this by treating the OpenWinClass=* case as a special case. In version 4.03, when the sandbox settings include OpenWinClass=*, the process is not put into a job, which means normal access to window objects, and the lower level requests are permitted.
This new special case is intended primarily at people who want to take advantage of filesystem/registry isolation when installing trusted programs into the sandbox.
To enable: Sandbox Settings > Resource Access > Window Access > Click Add, enter * (a single wildcard star), click OK.
This has two major implications:
- All interactions with window objects outside the sandbox have to go through a SbieSvc proxy process.
- Lower level requests such as simulating keyboard input, registering a hotkey or changing system parameters are not supported.
Version 4.03 revises this by treating the OpenWinClass=* case as a special case. In version 4.03, when the sandbox settings include OpenWinClass=*, the process is not put into a job, which means normal access to window objects, and the lower level requests are permitted.
This new special case is intended primarily at people who want to take advantage of filesystem/registry isolation when installing trusted programs into the sandbox.
To enable: Sandbox Settings > Resource Access > Window Access > Click Add, enter * (a single wildcard star), click OK.