Sandboxie Technologies (SBIE Open source) (VERSION 5.33.6 ONLY!)

The base version reaching an ignominious end ... the risk was there.

At least David is very active as a developer, and eminently reachable right here on Wilders.

 

The ones who looked into the issue (chromium) stated the same concerns, namely: security and stability while running Chrome (specifically) as was also firmly stated in this thread recently. They gave this issue quite a bit of respect, it seems. I appreciate that.

I'll continue to watch the Plus thread since, for a casual user like me, this workaround is just prolonging the inevitable viz 5.33.6. A miracle would be nice right about now....

 

The donate button takes me to PayPal where I login, then just see my home page. No option to pay by cc that I can see.

 

There are icons for Visa and master card and american express,
you can donate using a paypal button without owning a paypal account just using a regular credicard.

when you press the buttin you go to a paypal page that asks you if you want to donat using pp or a credit or debit card.

 

Windows 7 runs Chrome 86 and 5.33.6 just fine, afaik. Granted, not many are still running W7, but some of us are.

 

Thanks @stapp.

The summary was needed, especially for those not following the Sandboxie threads closely, because it's become a little 'messy'.

 

Sorry David, but it doesn't do that for me. If you want to pm your PayPal account details I will send funds directly,

 

More than a "little messy"! A dedicated forum is desperately needed IMO, but I understand why that is not an option currently.

 

Yes, I am having trouble trying to figure out how to send a payment also. This "simple mind" needs a simple way to make a one-time payment via credit card in U.S. dollars.
Thanks, Acadia

 

What exactly are the issues with running the last Sophos version and the latest Chrome?

 

I think the first report was by "catspyjamas" in this posting: https://www.wilderssecurity.com/threads/sandboxie-technologies-sbie-open-source.428156/page-19#post-2954444

From there on you will find various comments about the issue and various postings with the workaround, e.g. here:
https://www.wilderssecurity.com/thr...-sbie-open-source.428156/page-20#post-2955019

Thanks, stapp, for this excellent overview of the current possibilities concerning Sandboxie.

 

I would second that, also for windows 8. yesterday someone asked me about a different issue with sandboxie and a unity based game. No problems on win8, but same on win10 (1809) whatever which version of sandboxie. And when reading here all concerned users are running windows 10 at least. some of them another or additional security software. This raises the level for a solution from my view.

 

Many thanks to David : I have just installed v5.43.6 on my Win10 laptop, and everything's working great. Of course EAM first quarantined the installer, but I whitelisted it, and then it installed flawlessly.

 

Thank you Peter and Stapp - I actually don't have any issues on Chrome (yet) but interestingly this morning could not work out why Vivaldi is not loading anymore after an update I did. Never considered sandboxie to be related to the loading. With the work around, it's fine now but man, this is becoming more difficult every day.

 

Well obviously...

Look the excerpt from the chrome sources ...\chromium\src\sandbox\win\src\broker_services.cc

Code:

  // On Win10, jobs are associated via startup_info.
  if (base::win::GetVersion() >= base::win::Version::WIN10 && job.IsValid()) {
    startup_info->AddJobToAssociate(job.Get()); // <- here we break sandboxie 5.33.6 muhahahah....
  }

just kidding I added that comment LOL

 

Almost believed it, didn't see any typos.

 

Well, it's funny that on Win 8.1 and apparently also on Win 7 this problem didn't even exist, so there must be something on Win 10 that's different, perhaps some new sandboxing API?

It's indeed true that it's probably not the best idea to disable the browser's internal sandbox. However, don't forget that it's much more likely that you will encounter an attack on browsers than on Sandboxie. There are plenty of of remote code execution and sandbox escape vulnerabilities in browsers like Chrome and Firefox for example, so no matter if you disable the sandbox or not, without Sandboxie on top, you would be toast. Unless Sandboxie is specifically targeted as well.

 

Any progress with this project or it's just dead from the beginning?

 

Thanks for this, I was also getting confused a bit! For example, I saw the Sandboxie 5.43.6 version and didn't understand it because Tom never released it. But shouldn't it get a different name since 5.33.6 is still considered to be the Sandboxie Classic? And I also assume that Sandboxie Plus runs on top of the 5.43.6 version. And BTW, no surprise that the Chromium folks aren't willing to fix it.

 

IMO ~ 5.33.6 as last Sophos release = Legacy

https://github.com/sandboxie-plus/Sandboxie/releases/tag/v0.4.2
Classic UI
SandboxieInstall32-v5.43.6.exe
SandboxieInstall64-v5.43.6.exe
-
Plus UI
Sandboxie-Plus-x64-v0.4.2.exe
Sandboxie-Plus-x86-v0.4.2.exe
-------------------------

FWIW ~ last time I tried Sandboxie-Plus Setup overwrite 5.33.6 & 5.43.6 -
< The classical sandboxie release is installed, it must be uninstalled first.
Do you want to continue? >

 

Any advantages to using the Plus UI over the Classic?

lol! Scary!

 

https://github.com/sandboxie-plus/Sandboxie

https://www.wilderssecurity.com/threads/sandboxie-plus-sbie-fork.427755/page-26#post-2956467

https://www.patreon.com/m/2266874/posts