Skip to content
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.

Sign up for GitHub

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

Create ForceChildProcess.md #170

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Create ForceChildProcess.md #170

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5d7bb78
Create ForceChildProcess.md
love-code-yeyixiao May 19, 2024
75334e8
Update ForceChildProcess.md
love-code-yeyixiao May 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions PlusContent/ForceChildProcess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# ForceProcessChild

It was introduced after 1.14.0. When you start a new program in Sandman, select “Run outside the sandbox” in the sandbox selection window, and you'll see this option later.

## How does it work?

It is based on a process tracking mechanism.

## Can I use it in Classic Build?

Yes,you can.but you need to use command line.For example,"start.exe /box:DefaultBox /fcp Program.exe" could run a unsandboxed program named "Program.exe",and its child process will be forced into DefaultBox.

## Will any process it starts be sandboxed?

Yeah,but also no.Direct child processes opened through interfaces such as CreateProcess are sandboxed, but since they are not in the sandbox, we can not control the child processes that are indirectly opened through the DCOM or IPC interfaces.

### Un-shell explorer
Explorer is a typical example.When there is no explorer as shell running in the desktop,most of its child process will be forced.But if there is already a explorer as shell,the new explorer process will call the pervous explorer through DCOM,and then the shell explorer create a window that not controled by us,and the new process terminate by itself.