I've been using Sandboxie with Vivaldi for a long time. Sometimes it works, but more often they not it does not. The browser executes, but I don't have access to any of the extensions I need without using the "Template=Vivaldi_Profile_DirectAccess" line. I've even tried getting rid of that line and adding my own "OpenFilePath=" lines, so that there's no blanket allow. My question is, if I use "Template=Vivaldi_Profile_DirectAccess" than what's the point of using isolation at all since the entire profile directory is accessible? Is there a way I can access my extensions with sandboxie while not having that global allow permission?
The point is that the rest of your system is protected, to my understanding you want to have your extenstrions which are part of your profile but not the rest of the profile. The issue is not about installing extenssions from scratch inside the sandbox, right? If you allow the sandboxed vivaldi to have read access to your profile the extensions should work. but you can not allow read only to extensions and nothing else, you could selectively open the right files only to hide a portion of the profile but that woudl require a lot of handy work. Best is install the extensions to the sandbox directly to a new profile and if you want to have a box that auto clears on close, make a snapshot. Auto delete returns to the last snapshot on close.
I guess, I want to access my extensions without giving a global access rule to the rest of my profile. I've always viewed Sandboxie as a barrier between anything on my system that can access the internet and the rest of my system; allowing only what I chose to be written to the disk. Even way back in the tzuk days, that's the role I used sandboxie for. In this case, I don't want to give Vivaldi blanket access to the profile just so I can use extensions. Doing so would negate the purpose of using Sandboxie in the first place. From what I can tell, it sounds like you're saying the solution is snapshots. I'll admit, I've never used that feature and I'm not sure how they work. That's something I'll have to spend some time with.
I think I *might* have solved it. Using *\* at the OpenFilePath=vivaldi.exe, line seems to have done the trick. Without it, the same line does nothing. Curiouser and curiouser. Anyway, it seems to work now. That's odd because it was never needed before; I used to run Vivaldi just find. Some inner-workings of SBIE had to have changed. Hopefully the below line can help someone else wit the same issue. OpenFilePath=vivaldi.exe,C:\Users\[user]\AppData\Local\Vivaldi\User Data\Default\Extensions*\*
to know that this is the path to extensions content only (content from CRX). not settings or other data. this ofc has to fail someday.
Where to find this direct access setting again in SBIE Plus? I'm still using an older version of SBIE Plus and I don't think I gave Vivaldi direct access to the profile folder, and extensions still work. Cool that you have solved it.
It's listed as a part of the Vivaldi template. Go into your box settings, select app templates, and start typing "vivaldi" in the search bar. It'll be the first listing.
