-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
BreakoutProcess option does not work when opening files directly or using context menu options #3217
Labels
Confirmation Pending
Further confirmation is requested
Feature: Program Control
Issues with control structures
Comments
i cant reproduce the issue, |
When I opened the document this way, Code.exe crashed and the dump file was created in sandbox. (HOST, Windows 10 22H2) I will also try it in a virtual machine. (Hyper-V, Windows 11 22H2) |
Windows 11 22H2 (22621.1848) [Hyper-V]
sbiecode_20230824_163452.mp4 |
I have a similar issue, and especially the git.exe will be forced into sandbox. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Confirmation Pending
Further confirmation is requested
Feature: Program Control
Issues with control structures
Describe what you noticed and did
Steps:
BreakoutProcess=Code.exe
Notes:
PS>/path/to/file.txt
) works as expectedBreakoutProcess=*
orBreakoutFolder=*
DisableForceRules=y
I believe this is the same issue as #1883.
Log: vscode_sandboxie_open.zip
How often did you encounter it so far?
Always
Affected program
VS Code, git, krita, inkscape, ... (likely program-agnostic)
Download link
https://code.visualstudio.com/
Where is the program located?
The program is installed only outside the sandbox.
Expected behavior
when set as a BreakoutProcess, the process should not be sandboxed.
What is your Windows edition and version?
Windows 11 Home 10.0.22621 Build 22621
In which Windows account you have this problem?
A local account (Standard user)., A local account (Administrator).
Please mention any installed security software
Windows Security
What version of Sandboxie are you running?
1.9.2 & 1.10.5
Is it a new installation of Sandboxie?
I recently did a new clean installation.
Is it a regression?
Possibly? #1883 was closed as fixed in release 1.1.1
In which sandbox type you have this problem?
All sandbox types (I tried them all).
Can you reproduce this problem on a new empty sandbox?
I can confirm it also on a new empty sandbox.
Did you previously enable some security policy settings outside Sandboxie?
No
Crash dump
No response
Trace log
See above
Sandboxie.ini configuration
The text was updated successfully, but these errors were encountered: