Sandboxie Acquired by Invincea

I just keeping it disabled now, not that bothered going without it.

Just shows how bad the firefox code base is tho that a extension hitting a security restriction triggers a never ending memory leak.

To craig, you have a comment on allowing a memory cap been applied to a sandbox?

 

Memory cap? chrcoal, I read you mentioned something sort of similar to that a few days ago but there is nothing in Sandbox setting that have anything to do with memory. Your memory issue (if it only happens when you are running sandboxed) is related to using a conflicting extension or program that don't get along with SBIE. To fix this issue, you have to make the choice of uninstalling the conflicting program/extension or not using SBIE.

Bo

 

about @Overkill Chrome issues, i always run chrome sandboxed since ages, never got this issues, did you make a clean install of sandboxie free (means no traces of Sbie paid anywhere). Maybe an old setting of the paid version may conflicts.

about @chrcol issue , never got it too , i suggest him to remove all his security softs (clean install of Windows would be even better) , install sandboxie and run it again. Then see if the issue is still there. if not, then installing the security softs one by one and check if the issue reappears.

on my system, Sandboxie is the first security app i install and it works flawlessly every time; even after installing other security apps , i never get issue with it.

 

I rarely have an issue with Sbie, but when I do, it generally takes the system down with it requiring a hard shutdown

 

I just had it happen again...I was browsing and everything was running fine until I shut down chrome and after shutdown my system locked up again! This time in shadow mode (shadow defender).

 

No paid version ever on this machine

 

Beta 5.11.10 has been released.

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

Bo

 

5.11.10 ~ LUV to @invincea n' @Invincea

 

lol so many updates !

i will pass on this one

 

Beta 5.11.10 is looking pretty.

I given it a good ride tonight, I tested everything that I do in the sandbox everyday and cant find nothing wrong with it (XP). I ll do the same tomorrow in W7. Nice version.

Bo

 

Overkill, like Craig said, there is no difference between paid and free. Other than the features that get unlocked once the user registers their copy, all else is the same.

Try the new beta, sometimes just going from one version to the next fixes issues. And try doing it with your system as light as possible of other security programs and browser addons. You shouldn't be having any kind of issue running Chrome sandboxed in a W7 32 bits computer. Last week I tested Chrome in my W7 32 bits laptop, it felt really nice.

Bo

 

Thanks Bo

 

My joy, Overkill. You know, even though there is only one change reflected in the Change log that got posted with this version, the SBIE code has changed and perhaps more than what we can tell by what we read in the fixes. So, for someone like yourself who is an avid Sandboxie user and has an issue, it would behoove you to roll this version and see what happens.

And for someone like myself with no issues, when I see that there is a fix for printing in the change log, even though I don't have any issue printing, I want to test my printing right away cause the change in code could affect my printing. You never know. And if it does, I like to detect the precise version in which my issue has started so I can report it and have it fix. Good luck, Gator .

Bo

 

@bo elam et al,
Please remind me re sandboxA communication with sandboxB. For example discrete Firefox sandbox is active along with discrete Postimage (Desktop app) sandbox. I'm everyday browsing and everyday image edit including upload to postimage.org. Postimage sandbox is default with Drop Rights + Forced + Direct Access to Postimage History (AppData Local).
Can (mal) content in sandboxA communicate with sandboxB and vice versa.
Do sandbox's (same user account) cross talk, is cross talk a concern..?
http://postimg.org/image/ymqzuuoff/
Thanks

 

Hi bjm, when you are going to do sensitive browsing, its always best to stop all activities in all sandboxes. I use that as a rule. On this regard, Tzuk said:
"......it is still important to first stop all sandboxed activity in all sandboxes, for maximum protection."
http://www.sandboxie.com/index.php?DetectingKeyLoggers#defend

If I am not doing anything sensitive, having sandboxed activity in 2 or 3 sandboxes at the same time doesn't concern me. The key really is what are you doing.

I saw your picture. You are running two instances of Firefox in different sandboxes at the same time. Firefox might be running in different sandboxes but they have access to the same Firefox profile folder. One instance of Firefox can see a lot of what you are doing with the other instance.

Bo

 

Yes, for Firefox I have daily FF sandbox and safe FF sandbox. When I run safe FF, ...safe FF is the only active sandbox.
I became curious about Firefox and Postimage because they're web facing and access AppData. And (thinking) AppData is ubiquitous. And (further thinking) ubiquitous may be blabber mouth. Note: thinking is not my forte.

The "Key"....Hmm.....

 

C'mon, please. You exactly know what I meant.

Pretty much every single SBIE release address some Chrome issues. How many of those issue would go away if you and Google make a deal and disable Chrome build-in sandbox && annoying yellow bar. This currently wasted (yours) time spend on fighting with double sandboxing issues could be spend on other things and push SBIE development forwards. We would have MS Edge working already.

I could not believe my eyes when you wrote on SBIE forums that you didn't receive much requests about MS Edge working with SBIE. http://forums.sandboxie.com/phpBB3/viewtopic.php?p=120549#p120549

 

Sandboxie run sandboxed apps at "untrusted" integrity level; while Edge (and metro apps) run at a deeper and safer one (called Appcontainer, the windows' sandbox). Sandboxie isn't made to run a metro app, so it can't handle (at the moment) the Appcontainer level.

Chrome however can be tweaked to run at Appontainer level.

 

Not entirely true. It's all a stripped token, just a different implementation of that.

 

If we and Google work together.......Again, our working together is the Devs using the most current Dev build and internal tests. That's how this works. You honestly have no idea how this all works. And no, we don't work with MS directly, or anyone directly. Which is common. Companies don't share "trade secrets" with one another. You can't have a business by doing that.

And no, we haven't had many requests for Edge. Usually, a big push comes from commercial and enterprise..which uses SBIE tech in Invincea products.

Many haven't moved to Win 10. Let alone, Edge. As Companies transition from Invincea Endpoint to the new Invincea X, we shall see. That's if they also elect to have the SBIE based container as part of the "X" Suite. And that container only supports what the client wants it to support [say Office Doc and IE only in a container..]and that is all....it's highly tailored to the client for their specific need...unlike SBIE.

Edge and Metro apps are being looked into, but development is resource heavy.... And we don't have a hotline to Google, Microsoft, Mozilla, or anyone else.

 

Again, a BETA addresses concerns and problems the come up, the vast majority are Windows Fast Ring. I know this, as I test these...daily..and maintain the change logs. Chrome is there too. As are general tweaks.

And FYI... Google Chrome Devs are way out front in changing things. They're aggressive. This is why you see the changes in the beta. Of course, we are not going to not support easily the #2 [At times #1] browser used by SBIE customers according to internal data. Although, that depends...... Enterprise and business' stay conservative with IT and FF... Home users use Chrome, FF and many others. We very very little of Edge. Must home users have zero idea about Edge...they assume it's IE...SBIE will load IE if a home user forgets, and runs Sandboxed web browser [default Edge in 10] and so SBIE fires up IE. The vast majority have no clue. Which is a failing of MS IMHO.

Oh, and Enterprise / Commercial customers don't upgrade frequently. In fact, certain products they may use specifically blocks them from upgrading to a new browser build unless we already support it. Unlike SBIE, which people just update whenever the wind tells them too..and then are shocked, SHOCKED something doesn't work. But we do a good job keeping up. And the majority of our users use build 5.10 [Stable] or even OLDER.

 

Sandboxie is Sandboxie. Paid or otherwise. It's the EXACT SAME PROGRAM. The "paid" or "registered" version is just a license key. The "paid" features are there...and those features have zero to do with....anything. It's already installed when you install SBIE. The key just gives you the ability to use that which already is installed [Forced programs/folders, no nag screen, unlimited active SB, C2R support..] Thats it. Nothing to do with Chrome, or anything else. That code is SBIE.

There is no separate download or additional downloads.

Also, I see in your sig that you have known 3rd party security products [2 I see already] that are known to cause problems. And, there is no settings, none what so ever, that involves memory caps. I'd first look at those. http://www.sandboxie.com/index.php?KnownConflicts and http://forums.sandboxie.com/phpBB3/viewtopic.php?f=11&t=21539

 

I'd also suggest if you want SBIE Devs / support to address an issue, you post the question in the SBIE forums for them to look at. While there are fantastic people here, you also want to go straight to the source. As for the lock up issues, you'd be the first to have that sort of event. I don't even believe SBIE is capable of "locking" your system to the point you would have to resort to a hard shut down.

 

OK, so the new Invincea X product is without the container? Thanks for the confirmation. About Chrome and Edge, I can imagine it gets harder and harder for Invincea to support them because they already have their own sandbox.

 

Does anything changed in a way how sandboxed IE 11 treats group policy editor rules for latest 18 months? Where can I read how SBIE treats IE related GPOs?