The following issues were detected in this release and they will be fixed on v1.0.6: #1469 #1471

The 1.0.x line of builds is finally ready for a final release as version 1.0.5

The first major feature is Privacy Mode, here most of the PC is set to be treated like a Write[File/Key]Path meaning the sandbox locations are writable but the unsandboxed locations are not readable. The Hard disk appears empty except for C:\Windows and C:\Program Files and the registry only allows reading of the machine but not user root keys. This way sandboxed processes can work but can not access private user data.

To make this mode useful an other feature has been implemented called “Rule Specificity” it can be enabled independently but is always enabled in Privacy enhanced boxes. It allows to specify rules to override other rules, this is not based on specifying an order or priority, but instead by measuring how specific a rule is and always attributing the highest priority to the most specific rule.
Here the specificity is measures by the path length that matches the rule, except the last wildcard.

So for example the built in privacy rules plus a custom one
OpenFilePath=%AppData%\Mozilla\Firefox\Profiles*
NormalFilePath=C:\Program Files*
NormalFilePath=C:\Windows*
WriteFilePath=C:*
Here the rules are ordered by their specificity.
Also there is a new type Normal[File/Key/Ipc]Path which defines a default sandbox behavior for a path.

The next major feature is "App Compartment" mode "NoSecurityIsolation=y", this is a new mode of operation which disables the token based security isolation, which brings the security down to the level of other sand boxing solutions, but by doing so greatly improves compatibility. For all use cases where the goal is only compartmentalization, running multiple instances, etc, but not hard core security this mode is preferable as it should avoid many typical sandboxie issues caused by processes running with a heavily restricted token.
In this mode file system and registry accesses are still being filtered to enforce the access rules, this filtering can be disabled with "NoSecurityFiltering=y"

To ensure this “unsecure” mode is at least as secure as the sandboxing offered by other sandboxing products, a new object access filter was added that can be enabled with "EnableObjectFiltering=y" in the global settings.

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.

ChangeLog

[1.0.5 / 5.55.5] - 2021-12-25

Added

• sandbox top level exception handler to create crash dumps
  -- it can be enabled per process or globally using "EnableMiniDump=process.exe,y" or "EnableMiniDump=y" respectively
  -- the dump flags can be set as hex with "MiniDumpFlags=0xAABBCCDD"
  -- a preselected flag set for a verbose dump can be set with "MiniDumpFlags=Extended"
  -- Note: created dump files are located at: C:\Sandbox\%USER%\%SANDBOX%
• added template support for Osiris and Slimjet browsers (by Dyras) #1454

Changed

• improved SbieDll initialization a bit
• doubled size of Name_Buffer_Depth #1342
• improved text filter in the templates view #1456

Fixed

• fixed issue with forced process display #1447
• fixed crash issue with GetClassName #1448
• fixed minor UI issue #1382
• fixed UI language preset issue #1348
• fixed grouping issues in SandMan UI #1358
• fixed issue with EnableWin32kHooks #1458

Installers re-released with the following fix:

• fixed regression when launching Office apps #1468

[1.0.4 / 5.55.4] - 2021-12-20

Added

• Mechanism to hook Win32 system calls now also works for 32 bit applications running under WoW64
• Added customization to Win32k hooking mechanism, as by default only GdiDdDDI* hooks are installed
  -- You can force the installation of other hooks by specifying them with "EnableWin32Hook=..."
  -- or disable the installation of the default hooks with "DisableWin32Hook=..."
  -- Please note that some Win32k hooks may cause BSODs or undefined behaviour. (!)
  -- The most obviously problematic Win32k hooks are blacklisted, this can be bypassed with "IgnoreWin32HookBlacklist=y"
• added debug option "AdjustBoxedSystem=n" to disable the adjustment of service ACLs running with a system token
• added "NoUACProxy=y" option together with the accompanying template, in order to disable UAC proxy
  -- Note: Boxes configured in compartment mode activate this template by default
• added UI option to change default RpcMgmtSetComTimeout preset
• added Plus installer option to start the default browser under Sandboxie through a desktop shortcut
• added more entries to the Plus installer (current translations on Languages.iss file need to be updated)

Changed

• "EnableWin32kHooks=y" is now enabled by default, as no issues were reported in 1.0.3
  -- Note: currently only the GdiDdDDI* hooks are applied, required for Chromium HW acceleration
• Cleaned up low level hooking code a bit
• "RunRpcssAsSystem=y" is now auto applied for boxes in "App Compartment" mode when "RunServicesAsSystem=y" or "MsiInstallerExemptions=y" are present

Fixed

• fixed RPC handling in case a requested open service is not running #1443
• fixed a hooking issue with NdrClientCall2 in 32 bit applications
• fixed issue with start directory to run sandboxed when using SandMan #1436
• fixed issue with recovering from network share locations #1435

[1.0.3 / 5.55.3] - 2021-12-12

Added

• added mechanism to hook Win32k system calls on Windows 10 and later, this should resolve the issue with Chromium HW acceleration
  -- Note: this mechanism does not, yet, work for 32 bit applications running under WoW64
  -- to enable it, add "EnableWin32kHooks=y" to the global ini section, this feature is highly experimental (!)
  -- the hooks will be automatically applied to Chromium GPU processes
  -- to force Win32k hooks for all processes in a selected box, add "AlwaysUseWin32kHooks=program.exe,y" #1261 #1395

Fixed

• fixed bug in GetVersionExW making "OverrideOsBuild=..." not working #605 #1426
• fixed issue with some UTF-8 characters when used in the ini file
• fixed isolation issue with Virtual Network Editor #1102

[1.0.2 / 5.55.2] - 2021-12-08

Fixed

• fixed recovery window not refreshing count on reload #1402
• fixed printing issue introduced in 1.0.0 #1397
• fixed issues with CreateProcess function #1408

[1.0.1 / 5.55.1] - 2021-12-06

Added

• added checkboxes to most major box options lists
• added SumatraPDF templates (by Dyras) #1391

Changed

• rolled back change to "OpenClsid=..." handling
• made all major lists in the box options editable

Fixed

• fixed issue with read only paths introduced in 1.0.0
• fixed BSOD issue introduced in the 1.0.0 build #1389
• fixed multiple BITS notifications while running sandboxed Chromium browsers (by isaak654) ca320ec #1081
• fixed executables selection for "Run Menu" entries (by isaak654) #1379
• fixed SetCursorPos and ClipCursor ignoring DPI awareness (by alvinhochun) #1394

Removed

• removed Virtual Desktop Manager template (by isaak654) d775807 #1326

[1.0.0 / 5.55.0] - 2021-11-17

Added

• added Privacy enhanced mode, sandboxes with "UsePrivacyMode=y" will not allow read access to locations containing user data
  -- all locations except generic Windows system paths will need to be opened explicitly for read and/or write access
  -- using "NormalFilePath=...", "NormalKeyPath=...", "NormalIpcPath=..." allows to open locations to be readable and sandboxed

• added new "App Compartment" mode of operation, it is enabled by adding "NoSecurityIsolation=y" to the box configuration
  -- in this mode, security is traded in for compatibility, it should not be used for untrusted applications
  -- Note: in this mode, file and registry filtering are still in place, hence processes run without administrative privileges
  -- it is reasonably safe, all filtering can be disabled with "NoSecurityFiltering=y"

• added experimental use of ObRegisterCallbacks to filter object creation and duplication
  -- this filtering is independent from the regular SbieDrv's syscall-based filtering, hence it also applies to App Compartments
  -- with it enabled, an application running in a compartment will not be able to manipulate processes running outside the sandbox
  -- Note: this feature improves the security of unisolated App Compartment boxes
  -- to enable this feature, set "EnableObjectFiltering=y" in the global section and reload the driver
  -- when globally activated, the filtering can be disabled for individual boxes with "DisableObjectFilter=y"

• added "DontOpenForBoxed=n", this option disables the discrimination of boxed processes for open file and open key directives
  -- this behaviour does not really improve security anyways, but may be annoying, also app compartments always disable this

• added setting to entirely open access to the COM infrastructure

Changed

• reworked the resource access path matching mechanism to optionally apply more specific rules over less specific ones
  -- for example "OpenFilePath=C:\User\Me\AppData\Firefox takes precedence over "WriteFilePath=C:\User\Me"
  -- to enable this new behaviour, add "UseRuleSpecificity=y" to your Sandboxie.ini, this behaviour is always enabled in Privacy enhanced mode
  -- added "NormalFilePath=..." to restore default Sandboxie behaviour on a given path
  -- added "OpenConfPath=...", which similarly to "OpenPipePath=..." is a "OpenKeyPath=..." variant which applies to executables located in the sandbox
• removed option to copy a box during creation, instead the box context menu offers a duplication option
• reworked the box creation dialog to offer new box types

Fixed

• fixed SBIE1401 notification during Sandboxie Plus uninstall (by mpheath) 68fa37d
• fixed memory leak in driver handling FLT_FILE_NAME_INFORMATION (by Therzok) #1371