Sandboxie issue.
-
@Priest72 , I think about this too and I think the problems with Sandboxie are because of this, of putting an outdated application in a modern system.
-
Please see post here for what is happening.
I know it is down to new Vivaldi snapshot as I was browsing Sandboxed before I applied the update.
I am using Win 10 2004 19041.508
I can still run new Edge chromium browser under Sandboxie so it is definitely something Vivaldi related.
Issue also confirmed by another Vivaldi/Sandboxie user.
https://www.wilderssecurity.com/threads/sandboxie-technologies-sbie-open-source.428156/page-15#post-2950367
For those who don't like going to other forums from links...
Latest Vivaldi snapshot update 3.4.2049.2 has broken Sbie 5.33.6 for me. I cannot launch browser at all. Tried new Sandbox, reboot, etc etc.
The update contains a Chromium update to 86.0.4240.38 (perhaps that is responsible?)
I know it's the Vivaldi update as I can still use Sbie 5.33.6 on new EdgeA clue perhaps.
If I open Vivaldi sandboxed via right-click option on its ordinary desktop icon and select 'run sandboxed' nothing happens, spots appear and stay on sbie taskbar icon.
If I then right click on sbie taskbar icon and select to delete contents, there are files and folders to be deleted. So it must run if you do it that way but the webpage doesn't open.
If I open Sbie by clicking on the desktop icon for ''running default browser under the supervision of Sandboxie'', the sbie taskbar icon gets spots on the immediately closes. -
Does anyone know if the Chromium build 86.0.4240.38 which was installed in the latest Vivaldi snapshot 3.4.2049.2 is an experimental one?
I am still able to use Sandboxie with Edge Chromium but that is still on build 85.0.5641.51
I am trying to narrow down what part of the Vivaldi update broke Vivaldi for me and sandboxie.
-
@stapp said in Sandboxie issue.:
Does anyone know if the Chromium build 86.0.4240.38 which was installed in the latest Vivaldi snapshot 3.4.2049.2 is an experimental one?
Far as I know, all Chromium builds are experimental... there is no "stable" version.
-
-
@Hadden89
Don't really need to test chromium 85 as new Edge has that and it works fine with Sandboxie.I know it is something in Chromium 86 and the Vivaldi snalshot update that caused it as the minute I did the update Vivaldi wouldn't open sandboxied anymore.
-
@Gwen-Dragon I don't use sandboxie and have not for many years since i migrated to linux.I was just making this forum aware of such issue.
-
@Gwen-Dragon
First Sandboxie 5.33.6 is nothing to do with the fork setup by the dev here
https://github.com/sandboxie/sandboxie/issues5.33.6 is the last true version of the original Sandboxie before Sophos decided to release the source code.
It may be a bit tricky to do a bug report as Vivaldi won't open under Sandboxie. I (and others) are still trying various things to pin it down, but I will probably do a report later if we have no luck.
Thank for all input so far, it is appreciated. -
Looks like others are confirming my findings .
@Gwen-Dragon please see the 2 posts here -
@Gwen-Dragon
Bug report done. -
@Gwen-Dragon said in Sandboxie issue.:
@stapp Thanks for the report.
I tried to ping a dev to check this. Please ask me in a few days again.Any news?
Bug report [Jira] (VB-72301)
Just to show it is not just me having the issue .... -
Reporting that I have just updated Vivaldi to the next Snapshot version 3.4.2056.19.x64, and it also does not launch it in Sandboxie.
-
@Gwen-Dragon
Still no news? -
@Gwen-Dragon
''not unconfirmed''
What exactly does that mean ? -
Should the devs have difficulty finding the signed 5.33.6 Sandboxie installer it can be found here
https://community.sophos.com/sandboxie/f/forum/119347/announcing-sandboxie-5-33-6-release-and-open-source-update.
No one I know who uses the latest Vivaldi snapshot with Sandboxie 5.33.6 can open Vivaldi.
We are having to use another browser instead. -
@Gwen-Dragon, could you perhaps emphasise the importance of this issue to the developers. I believe that Vivaldi users are generally concerned about privacy and security, and Sandboxie, with its multiple sandboxes, is an excellent defence. It is unique amongst current software.
I have had to change my routines for many things back to Firefox, which I used previously. I mean banking particularly, but also taxation and shopping. It has all been a great nuisance, and if I lose confidence that Vivaldi is seeking a solution, I may have to take the easy way out and switch my standard browser back to Firefox, even though I much prefer Vivaldi.
I do understand that Vivaldi may not be able to fix the problem. Sophos bought Sandboxie and then abandoned it, and a solution many have to wait until one or other of the developing Sandboxie forks matures. Could we at least have an indication of Vivaldi's attention and concern --- 'if a dev has spare time' is not appropriate from them.
-
Chromium has it's own sandboxing technology built into their code.I would be very surprised if the chromium developers will create a fix for 3rd party sandboxing software which has the potential to break again further down the development line.Sandboxie may have been useful in the windows 7 era but as windows has progressed so has it's own sandboxing.There are alternatives like shadow defender etc.
-
@Gwen-Dragon, a simple partial workaround for Vivaldi, clearly explained, has now been posted on the Wilders website:
https://www.wilderssecurity.com/threads/sandboxie-technologies-sbie-open-source.428156/page-20It's not perfect, because it seems only to open Vivaldi in the default sandbox (although with attention to sandbox deletion, this is not a huge problem). Works for me.
Could the Vivaldi developers please get in touch with the techies posting on Wilders website and sort out what is to be done --- the simple workaround posted there seems to indicate to a non-techie like me that the issue is not too complicated. The issue now seems to be affecting all Chromium browsers as they follow Vivaldi in updating Chromium, and the workaround is reported to apply to some of them as well. It's not appropriate to avoid the issue by denigrating Sandboxie --- Vivaldi is all about giving choice and control back to the user.
-
@Gwen-Dragon, Thank you very much indeed for that warning. I am now quite out of my depth with all this, not being a techie, so could I suggest that you post your warning on the Wilders forum, where the method has been much discussed.
-
That workaround would only be temporary as the next chromium update would break it again,It is up to the sandboxie developer/s to make it compatible with chromium browsers and not the reverse,.At the moment there is a one man shop developing a sandboxie fork but as far as i am concerned sandboxie died the moment ronen left the project.