Announcing Sandboxie 5.33.6 release and open source update

What several bits of code were stripped away?

Only things related to licensing and software updating or something else?

I would presume that its other code related to functionality but one that due to legal reasons can't be open sourced.

i.e. the original author is not reachable or is not agreeing and the original license was limited to begin with.

Hence the test build to see if without or with a self written replacement code it still works as expected.

Don't presume anything and let's wait for the reply.

Thank you.

Does this build fix the bug reported here? https://community.sophos.com/products/sandboxie/f/forum/118874/sandboxie-5-33-3-now-available-for-download/432901#432901

If not then I will revert to 5.31.6 which apparently does not have this bug.

Thank you for all your effort in releasing SB to opensource.  It is appreciated.

Above post intended to be in reply to Pedro López.

We haven't stripped away any functionality from the Sandbox. As noted above, we had to clean up code that referenced things like licensing and remove any special integrations with OEM products. 

It would really help if you can provide feedback on the new build.

Akhilesh@Sophos

Akhilesh@Sophos said:

It would really help if you can provide feedback on the new build.

5.33.6 feels the same as 5.33.3

For me it seams to work just as fine as the previous build :D

Any ETA for the source release?

Please see this thread.  Apparently the bug reported there is still present in 5.33.6.

https://community.sophos.com/products/sandboxie/f/forum/118874/sandboxie-5-33-3-now-available-for-download

Akhilesh@Sophos said:

It would really help if you can provide feedback

What a coincidence! That's the same I've been thinking for months when I was seeing someone opening a thread and reporting a bug.

Well if you're going to be like that. we might as well give you the source code or something.

Akhilesh@Sophos

That error message is because Chrome no longer allows hooking of certain functions. For me hitting "Hide" hides the error and there are no ill effects.

Akhilesh@Sophos

That error message is because Chrome no longer allows hooking of certain functions. For me hitting "Hide" hides the error and there are no ill effects.

Akhilesh@Sophos

Akhilesh@Sophos said:

That error message is because Chrome no longer allows hooking of certain functions. For me hitting "Hide" hides the error and there are no ill effects.

Akhilesh@Sophos

 

Thank you for that explanation.  That presents a big problem for me since running Chrome in a sandbox is the main reason I use Sandboxie and for me, there are some problems.

When Chrome is sandboxed, I am unable to launch web pages from non-sandboxed applications or links in non-sandboxed applications.  Now I understand why.

When Chrome is run outside the sandbox I can launch web pages normally.  But when I run it in Sandboxie it doesn't work (it used to work fine a number of versions of SB and Chrome ago,but I just got a new PC and installed the latest versions of each and it is broken.).

This is a critical need for me.  So what you are saying is that there is no way for Sandboxie to get around this issue with Chrome since Sandboxie has no way of hooking the necessary functions?

If that's the case it appears there is no solution.

PS: I already switched from Firefox to Chrome over the last year or two because I couldn't find the right add-ins in Firefox to do what I needed to do after they changed to their Quantum build.  Now I finally have Chrome set up the way I like it.  But it's for naught if Sandboxie can't support it.  Not sure where I'll go next.

===========================

EDIT:

I am not sure this is the cause of the problem.  I found a workaround (that isn't very reliable but better than nothing).

If I launch Chrome first (sandboxed) and then try to launch a link in a non-sandboxed application (let's say Windows Wordpad), Chrome is not made active and the link is not loaded.

But it seems that if I start with Chrome closed, and then click the link in the non-sandboxed application it works.  Chrome is launched and the page is loaded.  Furthermore, if I then try to launch links from other non-sandboxed applications, while Chrome remains open from the first launch, they work too.  I have tried this several times and it seems to work, although I think I may have had the problem reoccur once when I tried it.  So it may not be perfect. 

So clearly Sandboxie CAN do this.  The problem may be unrelated to those messages.

Are there some SB settings that might affect this?

This sounds like the way the application is requesting the Web page server to be opened. Meaning it's the way the Chrome is being called/started outside of the sandbox.

Using a tool like Process Monitor (Procmon) can help understand how it's called.

Unfortunately there are no settings in Sandboxie that helps with outside but it might possible to adjust registry settings to get it to behave as you would normally.

Hello Akhile,

I gathered the Hooking Error Messages are Chrome related and you confirmed they do not imply potential security risk in SB. FYI, the same messages also show up when I sandbox the Brave Browser which is pretty much is based on Chromium open source.

I was wondering if you looked into the "security Certificate issues" when Sandboxing the MS Outlook as I and other folks reported. Any update on addressing them?

Thank You.