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.

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

AutoDelete isn't performed for forced programs in some sandboxes #1658

Closed
ksmustang opened this issue Feb 28, 2022 · 1 comment
Closed

AutoDelete isn't performed for forced programs in some sandboxes #1658

ksmustang opened this issue Feb 28, 2022 · 1 comment
Labels
Status: Fixed in Next Build Fixed in the next Sandboxie version

Comments

@ksmustang
Copy link

ksmustang commented Feb 28, 2022

What happened?

I have successfully used ForceProcess and AutoDelete in multiple sandboxes for many years. However, I created a new sandbox configured with AutoDelete and ForceProcess and the sandbox contents are not deleted when the lone program running in the sandbox is closed.

After much testing to isolate the problem, I've created a sample sandboxie.ini file that demonstrates the problem. The attached sandboxie.ini file contains" ForceProcess=notepad.exe". The sandbox contents aren't deleted when notepad is closed.

Note: The problem doesn't happen just for notepad.exe, I originally encountered the problem when sandboxing FoxitReader.exe (a PDF reader).

I have other sandboxes that use AutoDelete and one or more ForceProcess entries that autodelete properly, so I'm surprised the contents are not deleted for this sandbox.

To Reproduce

  1. Use the attached sandboxie.ini
  2. Run notepad.exe (notepad.exe will appear in the DefaultBox sandbox)
  3. Close notepad.exe

Expected behavior

The DefaultBox sandbox contents will be deleted after closing notepad.exe

What is your Windows edition and version?

Windows 10 21H1

In which Windows account you have this problem?

A local or Microsoft account without special changes.

Please mention any installed security software

Windows Defender (in virtual machine), ESET Internet Security (on host machine)

What version of Sandboxie are you running?

Sandboxie Plus 1.0.11

Is it a regression?

Unknown

List of affected browsers

Not applicable

In which sandbox type you have this problem?

In a Standard isolation sandbox (yellow sandbox icon).

Is the sandboxed program also installed outside the sandbox?

The sandboxed program is installed in the real system only.

Can you reproduce this problem on an empty sandbox?

I can confirm it also on an empty sandbox.

Did you previously enable some security policy settings outside Sandboxie?

No

Crash dump

No response

Trace log

No response

Sandboxie.ini configuration

[GlobalSettings]

[UserSettings_052E014C]
SbieCtrl_AutoStartAgent=SandMan.exe

[DefaultBox]
Enabled=y
BlockNetworkFiles=y
BorderColor=#00ffff,ttl,6
Template=OpenBluetooth
Template=SkipHook
Template=FileCopy
Template=qWave
Template=BlockPorts
Template=LingerPrograms
Template=Chrome_Phishing_DirectAccess
Template=Firefox_Phishing_DirectAccess
Template=AutoRecoverIgnore
ConfigLevel=9
BoxNameTitle=n
CopyLimitKb=81920
AutoDelete=y
ForceProcess=notepad.exe

Sandboxie-Plus.ini configuration (for Plus interface issues)

No response

@ksmustang
Copy link
Author

Apologies: the response for Is the sandboxed program also installed outside the sandbox? is incorrect. the program is installed in the real system only.

@DavidXanatos DavidXanatos added the Status: Fixed in Next Build Fixed in the next Sandboxie version label Mar 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Fixed in Next Build Fixed in the next Sandboxie version
Projects
None yet
Development

No branches or pull requests

2 participants