Sandboxie Acquired by Invincea

Rasheed187,

I've since wiped files but as I recall download file annotate as 32 or 64.
Note: AWFT pic unable to locate msi32 and other pic unable to locate msi64 #2576
Note: ran new default box with Run As.

 

Yes.

The only one SBIE issue I had with Firefox is related to theme bug in SBIE. It's known at least since Win7, so few years old. Try to open explorer in SBIE and right click on window's title bar. Theme won't apply correctly on Win7. On Win10 fonts in sandboxed explorer looks blurry.
After restoring PC from sleep mode, Firefox theme may not be applied correctly (tabs bar, buttons in right upper corner may go invisible or start blinking when you hoover your mouse over them).

http://i.imgur.com/xHJEp7A.png

 

I am not sure what your issue is in W7, but I cant see any difference on how the sandboxed Windows explorer looks as I compare it to when it runs unsandboxed. The pictures below show my sandboxed explorer as it runs and then how it looks when I right click the Windows title bar.



Bo

 

Yep, and compare context menu to unsandboxed explorer.

 

The only thing that I see different when I right click a file in a sandboxed or unsandboxed Windows explorer is that with the sandboxed explorer, I dont see the Run sandboxed option, which is not necessary as any file or exe will run sandboxed when you navigate to it using the sandboxed Windows explorer. Thats probably by design.



Bo

 

Sandboxed title's bar context menu theme looks more like classic theme than aero theme.
https://www.wilderssecurity.com/attachments/sin-titulo1-jpg.251955/
I see you're using windows basic theme which I didn't try.

In other words sandboxed Aero explorer title's bar context menu does not look the same as sandboxed one. This theme issue may affect other apps and other OSes.

 

I have a simple question.

I always use Firefox or Chrome with Sandboxie.
Recently, I've notice an interesting thing while using Chrome with Sandboxie.
I've checked Sandboxie's "Automatically Delete contents of sandbox" with Eraser, but...


When I restart Chrome, my cookies/history is still there.
Here is a snapshot before I close sandboxed Chrome:


Here is a snapshot when I restart Chrome:


What's more, it does not matter if I close with DELETION my sandboxed Chrome and RESTART Chrome with Sandboxie or without it.
The cookies are still there.
I've used Wise Cleaner Pro but the cookies were not removed.
I've tried CCleaner, and the cookies were gone.
I don't have any issues with removing cookies/history of sandboxed Firefox.
Any ideas on why Eraser does not remove sandboxed Chrome cookies/history?

 

The one thing I can think of is perhaps for Chrome you have Cookies set to be saved out of the sandbox. Check Sandbox settings>Applications>Web browsers>Google Chrome, make sure the setting to allow access to Cookies is unticked.

History gets saved if you tick the setting to allow access to Google Chrome bookmarks and history database.

I dont use Chrome but with Firefox if you allow bookmarks to be saved out of the sandbox, history gets saved as well. Thats because both, history and bookmarks gets saved by Firefox in the same file. What I do to get rid of history and stll be able to save bookmarks is to set Firefox to never remember history. You can try doing something similar with Chrome.

Bo

 

Thank you for your answer.
Here is my Chrome set in Sandboxie.

 

So, according to that picture, Cookies are not set to be saved out of the sandbox via Applications>Web browsers settings. Then perhaps they are being allowed via Sandbox settings>Resource access>File access>Direct access, select Chromeprograms in the Drop down Window, and see what it shows there.

You can also test using a new sandbox, to see if the behavior regarding cookies is different. It should be. In my view, this is a setting thing here, Zmechy.

About history. By ticking the allow direct access setting to save history database, your Chrome history goes out of the sandbox. Try doing what I do with Firefox regarding history.

Bo

 

Hi zmechys, interesting ones. Will be interested to see how this plays out.

Eraser should clean any files stored in the Sandbox at close-down. On Vista up Chrome stores cookies here - %Local AppData%\Google\Chrome\User Data\Default\Cookies so when Sandoxed (if you've not set to save them to the real system) they are stored here - Sandbox\Username\sandboxname\%Local AppData%\Google\Chrome\User Data\Default\Cookies. Eraser should pick this up and clean it.

The SBIE template you show for 'allow direct access to Chrome bookmark and history database' on Vista up allows files to be saved to the real system rather than sanboxed version at the following locations:

%Local AppData%\Google\Chrome\User Data\Default\Bookmarks*
%Local AppData%\Google\Chrome\User Data\Default\Thumbnails*
%Local AppData%\Google\Chrome\User Data\Default\*History*
%Local AppData%\Google\Chrome\User Data\Default\Current *
%Local AppData%\Google\Chrome\User Data\Default\Last *
%Local AppData%\Google\Chrome\User Data\Default\Visited Links*

None of that should allow cookies to be saved. Certainly setting it on my Chrome sandbox does not result in cookies being saved after the sandboxed browser is closed. That makes me think, like Bo, there is another Direct Access rule allowing this behavior.

It could of course be an Eraser issue or a slightly eroneous delete command. I have heard of problems with later versions of Eraser and SBIE. Guest10 gave some advice on the SBIE forums that may still be valid here http://forums.sandboxie.com/phpBB3/viewtopic.php?f=5&t=20784.

Regards

 

Here is my "chromeprograms"





Here is my Eraser working.


Here is my Sandoxie folder after Eraser deleted everything.



And here is my Sandboxed Chrome when I restarted it.

 

Zmechy, you should test running Chrome in a new sandbox with default settings. Don't copy settings from any existing sandbox when you create the new one. And do the test with default Delete command in Sandboxie. After running Chrome sandboxed and getting a few cookies in the sandbox, delete the sandbox.....and see what happens.

No cookies out, it means settings in the old sandbox are messed up somehow, if not, check Eraser. Perhaps the answer is in the link posted by Elwe.

Zmechy, as far as I can tell, in my systems cookies don't survive deleting the sandbox. No matter the browser. I always used default delete and never used programs for deleting cookies.

Bo

 

Please explain me are there any sense to use Drop Rights in a Standard User Account? I always wonder this using SBIE.

 

Solarlynx, I never used or tested an standard usrr account. I always run as an Administrator. After reading your post I am kind of tempted getting one going to see how programs work in the sandbox with or without Drop rights being enabled.

But this is what I would do if I was using an standard user account. I would try using Drop rights if programs can install in the sandbox without Drop rights being enabled. To me personally, that would be the tell tale sign that I would look for that would indicate to me that the setting does make a difference in the standard user account. Drop rights is supposed to keep programs from installing in the sandbox, it should stop malware from installing in non restricted sandboxes.

Test installing a browser or a video player in the sandbox, if it doesn't install or you get error messages (without enabling Drop rights), then the setting wont make a difference for you. If it installs, then yes, the setting can make a difference even in an standard user account. This is easy to test. I would prefer not to enable the guess account that comes with W7 to test, but I like to know what you find.

Bo

 

Something else about Drop rights. I try to use it whenever I can. But some programs in some computers work better in sandboxes without Drop rights. I have a couple of dedicated sandboxes where I don't enable Drop rights because the programs works better, smoother without the settings. Doing this doesn't bother me at all. So, I try using the setting whenever possible but its not the end of the world when I run a program without it. Thats my view.

Bo

 

Sandboxie Beta 5.11.1 has been released.

http://forums.sandboxie.com/phpBB3/viewtopic.php?f=57&p=119291#p119291

Bo

 

Salutations/Greetings!

Thank you, for letting us know about the update!

 

Thank you. I fulfilled your suggestion. I tried to install a few progs on my Standart User Account (SUA) and got the same results:
When "Drop Rights" are unchecked SBIE asks Admin permission and when I grant it then SBIE installs the prog inside.
When "DR" are checked then SBIE asks to uncheck it first in order to ask Admin previlege next.

So can we consider DR necessary on SUA?

 

Bo,

I have COMPLETELY uninstalled my Sandboxie and installed the newest version - 5.11.1, and all my problems are gone.
As I understand, there was some kind of glitch/bug.
Thank you for your help.

 

Yes, it certainly helps using it as your test proves.

Bo

 

You are welcome. I am glad to help, zmechy. I think your problem was due to your Sandbox settings or perhaps related to Eraser. When you click the uninstall option for Sandboxie, all your settings are removed. Starting with a new sandbox fixed the issue. I don't think there is a bug related to cookies.

Bo

 

Hi Moose, I am glad to do it .

Bo

 

Thank you. So Drop Rights gives additional security to Standart User Account.