-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add SpoolSV documenatation #163
base: main
Are you sure you want to change the base?
Conversation
Progresses sandboxie-plus#145 Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
Signed-off-by: Stavros Ntentos <133706+stdedos@users.noreply.github.com>
@@ -0,0 +1,28 @@ | |||
# Close Print Spooler | |||
|
|||
_ClosePrintSpooler_ is a sandbox setting that provided nuanced control over how sandboxed applications interact with the print spooler service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_ClosePrintSpooler_ is a sandbox setting that provided nuanced control over how sandboxed applications interact with the print spooler service. | |
_ClosePrintSpooler_ is a sandbox setting that provides nuanced control over how sandboxed applications interact with the print spooler service. |
|
||
Added as part of 0.5.4 / 5.46.0 version. | ||
|
||
_See also [ClosePrintSpooler](ClosePrintSpooler.md)_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_See also [ClosePrintSpooler](ClosePrintSpooler.md)_. | |
See also: [Close Print Spooler](ClosePrintSpooler.md). |
|
||
This setting can be used to prevent sandboxed applications from interacting with the print spooler service. When set to `y`, sandboxed applications will be unable to interact with the print spooler service - for example, print. | ||
|
||
Added as part of 0.5.4 / 5.46.0 version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This setting can be used to prevent sandboxed applications from interacting with the print spooler service. When set to `y`, sandboxed applications will be unable to interact with the print spooler service - for example, print. | |
Added as part of 0.5.4 / 5.46.0 version. | |
Added as part of 0.5.4 / 5.46.0 version. | |
This setting can be used to prevent sandboxed applications from interacting with the print spooler service. When set to `y`, sandboxed applications will be unable to interact with the print spooler service - for example, print. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know - usually the "added" is "the most useless part" of the documentation
(At least, when it is that wordy).
Does it make sense to emphasize it that much by putting it first?
While the project does not PUSH for updates, it is a "reasonable expectation" that users opt to update?
|
||
Added as part of 0.5.4 / 5.46.0 version. | ||
|
||
## Interaction with [OpenPrintSpooler](OpenPrintSpooler.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Interaction with [OpenPrintSpooler](OpenPrintSpooler.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree with that change.
I specifically opted in creating a "considerable" visual separator, to indicate that the ClosePrintSpooler
documentation has finished.
What follows is a "tangent"
OpenPrintSpooler=n | ||
``` | ||
|
||
When both settings are configured as shown above, requests from sandboxed applications to the print spooler are selectively filtered. This means that certain actions related to the print spooler are permitted ("open") while others are restricted ("closed"). Specifically, this configuration allows for printing operations but restricts activities that would modify printer configurations or the installation/removal of printers on the system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When both settings are configured as shown above, requests from sandboxed applications to the print spooler are selectively filtered. This means that certain actions related to the print spooler are permitted ("open") while others are restricted ("closed"). Specifically, this configuration allows for printing operations but restricts activities that would modify printer configurations or the installation/removal of printers on the system. | |
When both settings are configured as shown above, requests from sandboxed applications to the print spooler are selectively filtered. This means that certain actions related to the print spooler are permitted ("open") while others are restricted ("closed"). Specifically, this configuration allows for printing operations but restricts activities that would modify printer configurations or the installation/removal of printers on the system. | |
See also: [Open Print Spooler](OpenPrintSpooler.md). |
Progresses #145
Signed-off-by: Stavros Ntentos 133706+stdedos@users.noreply.github.com