Applications opened with "Alky for Applications" in WinXP SP3 escapes sandboxIE

Please post your problem description here

Moderator: Barb@Invincea

Post Reply
Aquila_XP
Posts: 1
Joined: Sat Jul 29, 2017 9:08 am

Applications opened with "Alky for Applications" in WinXP SP3 escapes sandboxIE

Post by Aquila_XP » Sat Jul 29, 2017 9:26 am

SandboxIE version 5.20
OS: Windows XP SP3 (x86)
Antivirus software: Avast 17.5.2303
Installed app: "Alky for Applications" is a plug-in for Window XP SP3 users to run Windows Vista applications.

I installed an app, that runs only on Win Vista+, in SandboxIE via Program Files.
When I right-clicked on that app, and in Context Menu I choosed "Patch and Run Vista executable...", I discovered in Task Manager that the application is running under current user and not under "ANONYMOUS LOGON" account.

Please fix this.

Best regards,
Aquila_XP

Barb@Invincea
Sandboxie Support
Sandboxie Support
Posts: 2337
Joined: Mon Nov 07, 2016 3:10 pm

Re: Applications opened with "Alky for Applications" in WinXP SP3 escapes sandboxIE

Post by Barb@Invincea » Mon Jul 31, 2017 12:47 pm

Hello Aquila_XP,

I installed Alky on a VM with XP SP3, then reboot as required by the steps. I then installed Opera inside a Sandbox, navigated to the installation path (wthin the Sandbox) , right-clicked on Opera and selected the Patch and run option. It launched Opera sandoxed / anonymous Logon. I also tested the "Run vista executable..." which also launched Sandboxed under Anonymous Logon.

What's the application that you are trying to run? Is Alky installed on your host?

Can you provide repro steps for the issue?

Regards,
Barb.-

Syrinx
Sandboxie Guru
Sandboxie Guru
Posts: 620
Joined: Fri Nov 13, 2015 4:11 pm

Re: Applications opened with "Alky for Applications" in WinXP SP3 escapes sandboxIE

Post by Syrinx » Mon Jul 31, 2017 1:41 pm

I also have a few questions if you don't mind...

Are you using a paid/activated version of sandboxie?
If no, is the program you are trying to launch via Alky installed outside of the sandbox? (The whole "via Program Files" part makes me think yes)
If yes, is the program you are trying to launch via Alky set up as a forced program or forced folder?

I tried it with Chrome 60 installed out of the box [copied an x86 version from a pre-installed one] and set as just a forced program & then just as a forced folder (paid features) in SBIE. While even Alky couldn't get it to *actually* run properly I was able to launch and test it enough before the dll errors started. Chrome was being forced in the sandbox even while using the 'Patch and Run Vista executable' context option on chrome.exe from the chrome application directory installed outside sandboxie for me.

I could see a usability problem if you are installing the program outside of the sandbox, are using the free version of sandboxie and are unable to use both 'Patch and Run Vista executable' along with the 'Run Sandboxed' context menu option at the same time but that's not even close to an 'escape' :-/
Goo.gl/p8qFCf

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest