[pre-commit.ci] auto-fixes from pre-commit hooks

sandboxie-plus · Sep 15, 2024 · 7145afc · 7145afc
1 parent bce1b27
commit 7145afc
Show file tree

Hide file tree

Showing 43 changed files with 23 additions and 43 deletions.
diff --git a/README.md b/README.md
@@ -14,4 +14,4 @@ After Sandboxie became [open source](https://news.sophos.com/en-us/2020/04/09/sa
 
 ## Contribute
 
-If you have development, testing or translation skills, then feel free to check out our [Contribution guidelines](https://github.com/sandboxie-plus/Sandboxie/blob/master/CONTRIBUTING.md).
+If you have development, testing or translation skills, then feel free to check out our [Contribution guidelines](https://github.com/sandboxie-plus/Sandboxie/blob/master/CONTRIBUTING.md).
diff --git a/custom_theme/css/theme_extra.css b/custom_theme/css/theme_extra.css
@@ -240,4 +240,4 @@ code {
 }
 .wy-nav-top a {
     font-weight:normal;
-}
+}
diff --git a/custom_theme/nav.html b/custom_theme/nav.html
@@ -22,4 +22,4 @@
         {%- endif %}
     </ul>
 {%- endif %}
-{%- set navlevel = navlevel - 1 %}
+{%- set navlevel = navlevel - 1 %}
diff --git a/docs/Content/BlockNetworkFiles.md b/docs/Content/BlockNetworkFiles.md
@@ -13,4 +13,4 @@ Specifying _n_ indicates that a sandboxed program may access network files witho
 
 Related Sandboxie Plus setting: Sandbox Options > Network Options > Other Options > Block network files and folders, unless specifically opened
 
-Related Sandboxie Plus setting when creating a new sandbox with "Configure advanced options" selected: Sandbox Isolation options > Network Access > Allow access to network files and folders
+Related Sandboxie Plus setting when creating a new sandbox with "Configure advanced options" selected: Sandbox Isolation options > Network Access > Allow access to network files and folders
diff --git a/docs/Content/BreakoutDocument.md b/docs/Content/BreakoutDocument.md
@@ -11,4 +11,4 @@ Usage:
    [DefaultBox]
    BreakoutDocument=C:\path\*.txt
    BreakoutDocument=C:\path\*.jpg
-```
+```
diff --git a/docs/Content/DropAdminRights.md b/docs/Content/DropAdminRights.md
@@ -19,4 +19,3 @@ Specifically, the security credentials used to start the sandboxed program will
 Note that this has little effect if you are already running under a non-Administrator user account.
 
 Related [Sandboxie Control](SandboxieControl.md) setting: [Sandbox Settings > Restrictions > Drop Rights](RestrictionsSettings.md#drop-rights)
-
diff --git a/docs/Content/InjectDll.md b/docs/Content/InjectDll.md
@@ -45,4 +45,3 @@ It is recommended to use the **hSbieDll** parameter as the module instance handl
 At this time, this setting cannot be manipulated from [Sandboxie Control](SandboxieControl.md). You have to manually edit it into [Sandboxie Ini](SandboxieIni.md).
 
 See also: [InjectDll64](InjectDll64.md), [SBIE DLL API](SBIEDLLAPI.md), [Start Command Line](StartCommandLine.md).
-
diff --git a/docs/Content/NtStatusCodes.md b/docs/Content/NtStatusCodes.md
@@ -8,4 +8,4 @@ Standard Windows NT Kernel Status Codes for Error Conditions:
 
 **C0000034** Object not found
 
-**C000009A** Insufficient system resources, typically indicates an out-of-memory condition
+**C000009A** Insufficient system resources, typically indicates an out-of-memory condition
diff --git a/docs/Content/OpenClsid.md b/docs/Content/OpenClsid.md
@@ -19,4 +19,4 @@ Related Sandboxie Plus settings:
 
 Sandbox Options > Resource Access > COM > Add COM Object > Access column > Open
 
-Sandbox Options > Resource Access > COM > Don't use virtualized COM, Open access to hosts COM infrastructure (not recommended)
+Sandbox Options > Resource Access > COM > Don't use virtualized COM, Open access to hosts COM infrastructure (not recommended)
diff --git a/docs/Content/Ransomware.md b/docs/Content/Ransomware.md
@@ -8,4 +8,4 @@ Not so with ransomware your important business data can be lost forever.
 
 Did you know that ransomware can hold your data hostage, and can't be stopped with anti-virus software alone?
 
-Sandboxie runs your programs in an isolated space which prevents malware - including ransomware - from making permanent changes to other programs and data in your computer.
+Sandboxie runs your programs in an isolated space which prevents malware - including ransomware - from making permanent changes to other programs and data in your computer.
diff --git a/docs/Content/RecoverySettings.md b/docs/Content/RecoverySettings.md
@@ -45,4 +45,4 @@ It may also be desirable to keep Immediate Recovery enabled, but exclude some fi
 
 Use this settings page to enable or disable the Immediate Recovery extension, and configure exclusions to Immediate Recovery.
 
-Related [Sandboxie Ini](SandboxieIni.md) settings: [AutoRecover](AutoRecover.md), [AutoRecoverIgnore](AutoRecoverIgnore.md).
+Related [Sandboxie Ini](SandboxieIni.md) settings: [AutoRecover](AutoRecover.md), [AutoRecoverIgnore](AutoRecoverIgnore.md).
diff --git a/docs/Content/SBIE1119.md b/docs/Content/SBIE1119.md
@@ -9,4 +9,3 @@
 The driver component of Sandboxie could not complete initialization. This message is issued when the internal logical device object which is used to control Sandboxie could not be created.
 
 This message is followed by message [SBIE1103](SBIE1103.md).
-
diff --git a/docs/Content/SBIE1120.md b/docs/Content/SBIE1120.md
@@ -8,4 +8,4 @@
 
 The driver component of Sandboxie could not complete initialization. This message indicates that Sandboxie could not identify the system service specified by _name_.
 
-This message is followed by message [SBIE1103](SBIE1103.md).
+This message is followed by message [SBIE1103](SBIE1103.md).
diff --git a/docs/Content/SBIE1152.md b/docs/Content/SBIE1152.md
@@ -6,4 +6,4 @@
 
 **Explanation:**
 
-Sandboxie could not allocate some memory.
+Sandboxie could not allocate some memory.
diff --git a/docs/Content/SBIE1211.md b/docs/Content/SBIE1211.md
@@ -8,4 +8,4 @@
 
 Whenever a program starts in a sandbox, Sandboxie has to complete a series of initialization steps which prepare the program to run successfully in the sandbox. This message indicates that one or more of these steps have failed.
 
-This is a summary message, and it follows one or more other error messages which indicate the precise cause of the error.
+This is a summary message, and it follows one or more other error messages which indicate the precise cause of the error.
diff --git a/docs/Content/SBIE1241.md b/docs/Content/SBIE1241.md
@@ -13,4 +13,3 @@ If yy is 11, the [KeyRootPath](KeyRootPath.md) setting may be improperly set, ca
 If yy is 22, the registry hive file may be corrupt, or the drive containing the registry hive file (and its associated sandbox) may be full.
 
 If yy is 33, the [FileRootPath](FileRootPath.md) setting may be improperly set, causing more than one sandbox to use the same registry hive file.
-
diff --git a/docs/Content/SBIE1405.md b/docs/Content/SBIE1405.md
@@ -13,4 +13,4 @@ Within each section, each line must be formatted as _name=value_.
 
 Alternatively, a line in the configuration file may be blank, or may begin with the hash character (#), in which case the line is considered a comment and is ignored.
 
-This message indicates that some text in the configuration file could not be parsed according to the syntax described above.
+This message indicates that some text in the configuration file could not be parsed according to the syntax described above.
diff --git a/docs/Content/SBIE2308.md b/docs/Content/SBIE2308.md
@@ -22,4 +22,3 @@ If you are running Sandboxie under a guest or limited user account, make sure th
 *   Make sure the guest or limited user account is listed for that entry
 *   Find the entry named "Create permanent shared objects"
 *   Make sure the guest or limited user account is listed for that entry
-
diff --git a/docs/Content/SBIE9101.md b/docs/Content/SBIE9101.md
@@ -7,4 +7,3 @@
 **Explanation:**
 
 The service component of Sandboxie (SbieSvc) was not able to complete some operation. The cause of the failure is insufficient system resources, typically memory.
-
diff --git a/docs/Content/SBIEMessages.md b/docs/Content/SBIEMessages.md
@@ -140,4 +140,4 @@ Some messages display details which include NT status codes, denoted in the help
 [SBIE9253](SBIE9253.md)
 [SBIE9302](SBIE9302.md)
 [SBIE9304](SBIE9304.md)
-[SBIE9305](SBIE9305.md)
+[SBIE9305](SBIE9305.md)
diff --git a/docs/Content/SandboxHierarchy.md b/docs/Content/SandboxHierarchy.md
@@ -104,4 +104,3 @@ The free utility [WinObj](https://docs.microsoft.com/en-us/sysinternals/download
 Unlike the case with files or registry keys, sandboxed programs are never permitted to access IPC objects outside the sandbox namespace, not even for read-only access. This behavior can be affected with the registry-related settings [OpenIpcPath](OpenIpcPath.md) and [ClosedIpcPath](ClosedIpcPath.md).
 
 Note that Sandboxie includes a number of built-in [OpenIpcPath](OpenIpcPath.md) settings to allow programs to function correctly, and in a typical system, more [OpenIpcPath](OpenIpcPath.md) settings are applied through compatibility settings for third-party software.
-
diff --git a/docs/Content/SandboxieLogon.md b/docs/Content/SandboxieLogon.md
@@ -1 +1 @@
-# Sandbox SID
+# Sandbox SID
diff --git a/docs/Content/TokenMagic.md b/docs/Content/TokenMagic.md
@@ -24,4 +24,4 @@ To eliminate the dependencies on unexported symbols, it would be required to pro
 
 I have not investigated if it would be feasible to do the token replacement before it gets officially frozen.
 
-Other than the above essential dependencies, Sandboxie gets the Clipboard object from the window station object in order to adjust the integrity level for the stored items such that they can be accessed by the sandboxed applications.
+Other than the above essential dependencies, Sandboxie gets the Clipboard object from the window station object in order to adjust the integrity level for the stored items such that they can be accessed by the sandboxed applications.
diff --git a/docs/Content/ViewMenu.md b/docs/Content/ViewMenu.md
@@ -12,4 +12,4 @@ The Files and Folders selects [Files And Folders View](FilesAndFoldersView.md),
 
 ## Context Menu
 
-The Context Menu commands displays the context menu associated with the item that is highlighted (selected). The context menu can also be displayed by clicking the right mouse button on an item. An item is a sandbox, a program, a file or a folder. Not all items appear in all views.
+The Context Menu commands displays the context menu associated with the item that is highlighted (selected). The context menu can also be displayed by clicking the right mouse button on an item. An item is a sandbox, a program, a file or a folder. Not all items appear in all views.
diff --git a/docs/Content/YesOrNoSettings.md b/docs/Content/YesOrNoSettings.md
@@ -6,4 +6,4 @@ To indicate the setting is enabled (or selected, or yes), specify Y.
 
 To indicate the setting is disabled (or unselected, or no), specify N.
 
-A boolean setting which not specified, or specifies some other value other than Y or N will silently revert to a default value which depends on the particular setting. For example, the default value for the [OpenProtectedStorage](OpenProtectedStorage.md) setting is N.
+A boolean setting which not specified, or specifies some other value other than Y or N will silently revert to a default value which depends on the particular setting. For example, the default value for the [OpenProtectedStorage](OpenProtectedStorage.md) setting is N.
diff --git a/docs/PlusContent/DNSFilter.md b/docs/PlusContent/DNSFilter.md
@@ -24,4 +24,4 @@ The logging component of this feature offers users the opportunity to monitor DN
 The mechanics of DNS Query Control are elegantly intricate. Users can selectively block or redirect DNS queries made by sandboxed programs for specific domains. This process involves defining rules within the sandbox configuration, dictating how DNS queries to certain domains should be handled. This level of granularity empowers users to tailor the DNS experience within the sandboxed environment according to their security and privacy preferences.
 
 ## Embrace the Future of Network Control
-DNS Query Logging, Filtering, and Redirection transcends traditional sandboxing capabilities. It introduces an unprecedented level of network oversight, effectively placing users at the helm of their sandboxed network interactions. In an age where data security, privacy, and control are paramount, this feature stands as a beacon of innovation. Join us in embracing the dawn of network control with DNS Query Logging, Filtering, and Redirection – where every DNS interaction is precisely managed to align with your security vision.
+DNS Query Logging, Filtering, and Redirection transcends traditional sandboxing capabilities. It introduces an unprecedented level of network oversight, effectively placing users at the helm of their sandboxed network interactions. In an age where data security, privacy, and control are paramount, this feature stands as a beacon of innovation. Join us in embracing the dawn of network control with DNS Query Logging, Filtering, and Redirection – where every DNS interaction is precisely managed to align with your security vision.
diff --git a/docs/PlusContent/Plus-Features.md b/docs/PlusContent/Plus-Features.md
@@ -95,4 +95,4 @@ Some more features (**) are available to participants of the [Sandboxie-Insider]
 #### ARM64 support for Windows 11 *
  - Support ARM64 natively
  - Support emulated x86
- - Support emulated x64 (ARM64EC)
+ - Support emulated x64 (ARM64EC)
diff --git a/docs/PlusContent/ProxySupport.md b/docs/PlusContent/ProxySupport.md
@@ -24,4 +24,4 @@ For security-conscious users, Proxy Injection becomes a vital tool for observing
 The mechanics of Proxy Injection are elegantly simple, yet profoundly effective. Users can designate specific applications (or entire boxes) to undergo proxy injection, effectively compelling these applications to establish their network connections through the selected Socks 5 proxy. The result is a controlled network environment that aligns with security and privacy preferences, effectively mitigating potential vulnerabilities that might arise from direct connections.
 
 ## Embrace the Future of Network Control
-Proxy Injection emerges as a visionary feature that redefines network interaction paradigms within sandboxed environments. It transforms the sandboxing experience by offering users granular control over how applications access external resources. As we forge ahead in an era where digital security is paramount, Proxy Injection emerges as a powerful tool that empowers users to safeguard their interactions, maintain privacy, and proactively manage application behavior. Join us in embracing the future of network control with Proxy Injection – where every connection is made on your terms.
+Proxy Injection emerges as a visionary feature that redefines network interaction paradigms within sandboxed environments. It transforms the sandboxing experience by offering users granular control over how applications access external resources. As we forge ahead in an era where digital security is paramount, Proxy Injection emerges as a powerful tool that empowers users to safeguard their interactions, maintain privacy, and proactively manage application behavior. Join us in embracing the future of network control with Proxy Injection – where every connection is made on your terms.
diff --git a/docs/PlusContent/Sandboxie-Insider.md b/docs/PlusContent/Sandboxie-Insider.md
@@ -24,4 +24,3 @@ Please note that:
 - Experimental things that may impact compatibility are tested in the public GitHub preview channel.
 - The Sandboxie Plus insider builds are based on stable final releases, with new functionality added on top.
 - The insider builds are compiled with Qt6 and provided as a unified x64/ARM64 installer.
-
diff --git a/docs/PlusContent/Sandboxie-Live.md b/docs/PlusContent/Sandboxie-Live.md
@@ -25,4 +25,3 @@ There is no "Ignore" option for "New Version", as that is covered by disabling t
 In the "Stable" channel, a check for "Version Update" is only available to supporters with a valid certificate. In this channel, all updates are signed and consist of the latest compatibility templates and urgent bug-fixes and translations.
 
 In the "Preview" channel, the "Version Update" consists of unsigned test builds (except the signed driver) released every few days (like 1.6.0, 1.6.1a and 1.6.1b), as here the updates contain not only half-tested fixes but also new functionality which may not yet be free of bugs.
-
diff --git a/docs/PlusContent/USBSandboxing.md b/docs/PlusContent/USBSandboxing.md
@@ -13,4 +13,3 @@ Sandboxie-Plus introduces USB Drive Sandboxing, a new and impactful feature with
 - Data Integrity: Even in the presence of a potentially unsafe USB drive, your data remains intact while the malicious process is confined to the sandboxed environment.
 
 Embrace a more secure future with USB Drive Sandboxing – a feature that revolutionizes your approach to external storage security, mitigating risks and reinforcing your system's defense mechanisms.
-
diff --git a/docs/PlusContent/applying-supporter-certificate.md b/docs/PlusContent/applying-supporter-certificate.md
@@ -25,4 +25,3 @@ Once the certificate is accepted, the entry field should become green:
 ![](../Media/PlusCert6.png)
 
 And a notification popup window should appear.
-
diff --git a/docs/PlusContent/black-box.md b/docs/PlusContent/black-box.md
@@ -1,4 +1,3 @@
 # Black Box
 
 TODO
-
diff --git a/docs/PlusContent/box-preset-comparison.md b/docs/PlusContent/box-preset-comparison.md
@@ -14,4 +14,3 @@ Sandboxie Plus can also be used to [protect confidential data](../PlusContent/bl
 |![](../Media/sandbox-c-full.png) Cyan Box|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|![Green Color](https://placeholder.antonshell.me/img?width=15&color_bg=green&text=+) YES|![Green Color](https://placeholder.antonshell.me/img?width=15&color_bg=green&text=+) YES|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|
 |![](../Media/sandbox-g-full.png) Green Box|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|![Green Color](https://placeholder.antonshell.me/img?width=15&color_bg=green&text=+) YES|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|
 |![](../Media/sandbox-k-full.png) Black Box|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|![Red Color](https://placeholder.antonshell.me/img?width=15&color_bg=FF0000&text=+) NO|![Green Color](https://placeholder.antonshell.me/img?width=15&color_bg=green&text=+) YES|![Green Color](https://placeholder.antonshell.me/img?width=15&color_bg=green&text=+) YES|![Green Color](https://placeholder.antonshell.me/img?width=15&color_bg=green&text=+) YES|
-
diff --git a/docs/PlusContent/compartment-mode.md b/docs/PlusContent/compartment-mode.md
@@ -17,4 +17,3 @@ A new object access filter, enabled by default for new installations since **San
 **Recent Changes:** Token based workarounds were added in subsequent Sandboxie Plus versions to facilitate even greater compatibility with the more commonly used programs. They used `DropAppContainerToken=y` for such workarounds and `FakeAppContainerToken=program.exe,n` to disable their use for a specific program. In **Sandboxie Plus v1.8.2a** and above, such workarounds are disabled when in compartment mode. In case of issues with some programs (primarily browsers), they can be re-enabled by using `DeprecatedTokenHacks=y`. **Sandboxie Plus v1.8.0** moved the built-in access rules for an application compartment box to a dedicated template (included in the file **Templates.ini** under the `[TemplateAppCPaths]` section) for easier management. **Sandboxie Plus v1.10.1** addressed and fixed various long-standing bugs affecting application compartment boxes.
 
 **Fun Fact (for any box type):** If you add `OpenFilePath=*` to the box settings section of **[Sandboxie Ini](../Content/SandboxieIni.md)** (or disable the isolation in some other way), the status column in the Sandman UI displays **OPEN Root Access** as a warning that this box is no longer really a "sandbox"! Starting with **Sandboxie Plus v1.3.2**, the box icon also changes its default color.
-
diff --git a/docs/PlusContent/imdisk.md b/docs/PlusContent/imdisk.md
@@ -1,4 +1,3 @@
 # ImDisk
 
 TODO
-
diff --git a/docs/PlusContent/privacy-mode.md b/docs/PlusContent/privacy-mode.md
@@ -28,4 +28,3 @@ Internally, a privacy enhanced box is based on three defaults:
 - Internally, rule specificity is **always enabled** in privacy mode. It uses the **[Normal](../Content/NormalFilePath.md)** path directive (`Normal[File/Ipc/Key]Path`) to open selected locations to be **readable and sandboxed**. Note that setting a path to normal is meaningful only when a parent path was first set to something else, as done in privacy mode. It is thus relevant not only for **blue**  boxes (based on privacy mode) but also for **red** boxes (with both privacy mode **and** [security mode](../PlusContent/security-mode.md) enabled).
 
 **Recent Changes:** Upon the introduction of privacy mode, a few built-in access rules were offered for some of the more common browsers and applications and these were augmented in later versions. Starting with **Sandboxie Plus v1.8.0**, all built-in access rules have been moved to a set of default templates (included in the file **Templates.ini** under the `[TemplatePModPaths]` section) for easier management.
-
diff --git a/docs/PlusContent/sandboxie-plus.md b/docs/PlusContent/sandboxie-plus.md
@@ -3,4 +3,3 @@
 Since the open sourcing, Sandboxie is being released in two flavors: the Classic build with a [MFC](https://en.wikipedia.org/wiki/Microsoft_Foundation_Class_Library)-based UI and a Plus build that incorporates new features with an entirely new [Qt](https://www.qt.io/)-based UI. All newly added features target the Plus branch, but can often be utilized in the Classic edition by manually editing the [Sandboxie Ini](../Content/SandboxieIni.md) file.
 
 The full Sandboxie documentation can be found through the [Support Page Index](../Content/AllPages.md), or you can start directly with the [Help Topics](../Content/HelpTopics.md) overview.
-
diff --git a/docs/PlusContent/sandboxie-portable.md b/docs/PlusContent/sandboxie-portable.md
@@ -1,4 +1,3 @@
 # Sandboxie-Portable
 
 TODO
-