![]() |
| 'Your Uninstaller' Starts Outside Sandbox? |
|
D1G1T@L
|
go to SBIE Control > File> Is window sandboxed? then drag the cursor over to the program. This is the best way to tell if the program was isolated or not.
|
||||||||||||
|
_________________ One Program to rule them all, One Program to confine them, One Program to wrest them all and in the sandbox bind them. |
|||||||||||||
|
AES
|
Great tip D1G1T@L, and using the method you mentioned Sandboxie reports that 'Your Uninstaller' is not running as part of any sandboxed program. And I actually see Your Uninstaller in the Start Menu on my system(outside the sandbox).
I also noticed that Sandboxie Control main window shows nothing is running in the 'Your Uninstaller' sandbox after I launched it. Enabling/Disabling Drop rights for the 'Your Uninstaller' Sandbox seems to have no effect in this case. Do you have an idea why 'Your Uninstaller' starts outside of the Sandbox? Is it because it uses and requires admin user rights to launch? I am being very careful with this software because my AV has been detecting spyware/trojan elements in the recent updated installers. |
||||||||||||
|
|
|||||||||||||
|
Guest10
|
Tested on XP; not on Win 7; SB 3.68
I installed "Your Uninstaller! 7" in a sandbox during a virtual session, in case I had your experience of some items showing up outside of the sandbox. I couldn't find anything that was outside, though. It's not on my Start Menu, Add/Remove Programs, or in "Program Files" outside of the sandbox. I have to start it from the Sandboxie Start Menu.
---- As an aside, I don't think much of them pre-selecting an option that installs a toolbar and selects a new home page and search provider. And then they want to install WeatherBug. I hope you unchecked or Decline(d) all of it. I didn't think much about their installer not letting me know what was going on during the long install process. And it installed "AVG Secure Search" and runs "vprot.exe" after the install, even though I'm sure that I declined it during the install. |
||||||||||||
|
_________________ Paul XP Pro SP3 (Admin rights), Zone Alarm Pro Firewall, Malwarebytes Pro, Firefox 21, Thunderbird 17 |
|||||||||||||
|
D1G1T@L
|
Keep in mind that in the past some (malicious?) programs were reported as able to evade the right click run sandboxed option. The one surefire way to make sure that it does run in a protected fashion is to run it from a sandboxed windows explorer instance. To make it more convenient go to the shell integration options from the configure emnu and create a shortcut for explorer from there; assoc. it with the sandbox of choice.
|
||||||||||||
|
|
|||||||||||||
|
AES
|
Thanks for the helpful replies guys, and I had a chance to test out Your Uninstaller behavior in both a VM and a Physical Machine.
@Guest10 After further investigation, I think you are correct about no settings/data being written to the physical machine(also checked appdata). It showed up on my start search because I had pinned it to the start menu, my bad. If I hadn't received this app as a gift, I would just avoid this in total--I hate spyware/toolbar bundle bs too!!! @D1G1T@L Creating the shortcut using Window Shell Integration works perfect and launches in the sandbox every time! Thanks for the tip! I tested two other apps that requires admin rights to start(XVid4PSP5 and Total Uninstall Trial), and both of them starts outside the sandbox if i pin the taskbar icon directly from "Explore Contents". |
||||||||||||
|
|
|||||||||||||
|
AES
|
I have one question:
If I decide to use the "Your Uninstaller" in a sandbox, how would I setup the restrictions so the program can uninstall programs in the un-sandboxed physical system? File Access > Full > Select Drives with Programs installed Registry Access > ? |
||||||||||||
|
|
|||||||||||||
|
Helper
|
Even though this is normally a complete no-no, there is an advantage in having the program running in this way. You can delete the sandbox and get rid of it and whatever changes it would normally have made to your system during an install, but allow it to do it's job in the meantime - assuming that you trust it to do whatever it wants to do, outside of the sandbox. I assume that's what you have in mind. |
||||||||||||||||
|
|
|||||||||||||||||
|
AES
|
You my friend, are a mind reader Does adding the asterisk (*) work for setting other restrictions as well? (Example: File Access > Direct > *) If I grant a sandbox program full file access to the un-sandboxed system, I also grant it the ability to write appdata and temp files outside the sandbox, is this correct? |
||||||||||||||
|
|
|||||||||||||||
|
Helper
|
|
||||||||||||||||
|
|
|||||||||||||||||
|
AES
|
Thank you Helper
|
||||||||||||
|
|
|||||||||||||
| 'Your Uninstaller' Starts Outside Sandbox? |
|
||
|


Use the RSS feed to watch this topic for replies