Sandboxie Support

When running Firefox "Quantum" sandboxed, it appear that changes made to permissions in the new NoScript do not get permanently saved. (At least they do not remain after closing and re-opening Firefox.) My old NoScript permissions from before the upgrade still seem to be there, however, and I did not have this problem before the upgrade. Has something changed that needs to be reflected in a modified Sandboxie configuration?

Hello jclarkw,

Can you please provide the settings that you are using along with:
viewtopic.php?f=11&t=19746

Does the issue happen in a new Sandbox with default settings?
I tested giving access to the Firefox profile, and NoScript worked. So if you can provide your settings, I'll test them and see what needs to be updated.

Regards,
Barb.-

jclarkw wrote: ↑

Thu Dec 21, 2017 11:49 am

When running Firefox "Quantum" sandboxed, it appear that changes made to permissions in the new NoScript do not get permanently saved. (At least they do not remain after closing and re-opening Firefox.) My old NoScript permissions from before the upgrade still seem to be there, however, and I did not have this problem before the upgrade. Has something changed that needs to be reflected in a modified Sandboxie configuration?

Hi jclark, there is no conflict between Sandboxie and NoScript 10. I am using NoScript 10 in W7 and W10.

If you want to save NoScript 10 settings out of the sandbox, you need to allow Firefox Direct file access to file "storage-sync.sqlite", this file is located inside your Firefox profile folder. Pre NoScript 10, NS saved data in prefs.js, but that changed in Firefox 57 with the release of NoScript 10.

Bo

>>If you want to save NoScript 10 settings out of the sandbox, you need to allow Firefox Direct file access to file "storage-sync.sqlite", this file is located inside your Firefox profile folder.<<


Bo -- Thanks! This sounds like the right answer, but I'm afraid I need a little more hand-holding:

1) Do you mean to add something like the red line in a block like the following, dating from earlier versions?

"[Template_Local_Firefox_Addons_NoScript_AdBlockPlus_NoSquint]

Tmpl.Title=Misc Add-ons for Firefox
OpenFilePath=firefox.exe,*\adblockplus\*
OpenFilePath=firefox.exe,*\prefs.js
OpenFilePath=firefox.exe,*\storage-sync.sqlite
OpenFilePath=firefox.exe,*\NoScriptSTS.db
OpenFilePath=firefox.exe,*\ABE\Rules\*
Tmpl.Class=Local"

2) Is the line below it (OpenFilePath=firefox.exe,*\NoScriptSTS.db) still necessary?

3) While we're at it, do you know if the AdBlockPlus line in the same block is still correct?

4) In general, can you point me to instructions for how to do this kind of tinkering and what it means?

Thanks again, and Happy Holidays! -- jclarkw

Open Sandbox settings>Resource access>File access>Direct access, Click Drop down window, Click on Firefox, Click Add, navigate to the files you need to allow access for NoScript and Adblock plus by following the paths below:

In Firefox 57, for NoScript, you need to allow access to "C:\Users\jclark\\AppData\Roaming\Mozilla\Firefox\Profiles\xxxx.default\storage-sync.sqlite

In Firefox 57, for Adblock plus, you allow access to "C:\Users\jclark\AppData\Roaming\Mozilla\Firefox\Profiles\xxxx.default\browser-extension-data\{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}\storage

In Firefox 57, there is no need anymore to allow access to prefs.js for ABP or NoScript but you might want to allow access to it for changing some Firefox settings or about:config. You can disregard any other file you listed for NoScript or ABP as they dont apply for Firefox 57 and the addons. HTH, J.

Bo

Thank you for the clear explanation. -- jclarkw

You are welcome, jclarkw. I am happy to help.

Bo