Self-Destruct-Cookies for Firefox and a few other things

[Baldape]

Recently I decided to try Self-Destruct-Cookies so I spoke with the developer about where it saves it's white list to and he told me that I need to save the permissions.sqlite outside sandbox.
Now I know that if I go to sandbox>default>sandbox settings>resource access>file access>direct access and select Firefox>add>C-drive>users>app-data>roaming>Mozilla>Profiles>default>permissions.sqlite but the problem with that method is that it would be locked to just that user account only correct?
By the way 'should' or do I need to auto delete cache when closing FF when saving cookies outside SBIE and if I auto delete active log-ins will I lose my cookies,passwords or history?


One more thing if I remember correctly the file path for FF phishing data was altered recently so how do add this new path into SBIE?

[Guest10]

Disclaimer:
I have no experience with user accounts, since I'm the only user on my computer.

I think that you left out a folder that would be in the path.
You listed:
C-drive>users>app-data>roaming>Mozilla>Profiles>default>permissions.sqlite
I believe it is actually:
C:\Users\(user)\AppData\Roaming\Mozilla\Profiles\xxxxxxxx.Default\permissions.sqlite
and it would also include the full name of the Firefox profile folder, shown above with "xxxxxxxx.Default".

Sandboxie would create a setting like this if you used the procedure you listed:
OpenFilePath=firefox.exe,%AppData%\Mozilla\Firefox\Profiles\xxxxxxxx.Default\permissions.sqlite
so the setting would apply to all users because of the %AppData% variable.

However, the question arises as to whether the full name of the Firefox profile folder is the same for all users.
In the above lines I used "xxxxxxxx.Default" as an example, but does each user have the exact same name for their Firefox profile folder? I don't know that, since I'm the only user, but I suspect that each user would have a different name for their "Default" profile (the "xxxxxxxx." part of their profile folder's name).
One alternative would be to edit the setting and use a wild card (*) in place of the profile folder name:
OpenFilePath=firefox.exe,%AppData%\Mozilla\Firefox\Profiles\*\permissions.sqlite

If all users can use any of the sandboxes that have been created in Sandboxie's configuration file, it would seem to be better to use a generic (wild card) setting for that sandbox - one that does not depend on the path to the "permissions.sqlite" file.
Sandbox Settings > Resource Access > File Access > Direct Access
"Add Program" button: firefox.exe
"Edit/Add" button: *\permissions.sqlite
OK
Resulting in:
OpenFilePath=firefox.exe,*\permissions.sqlite

So each person who uses a sandbox with that setting will be allowing the "permissions.sqlite" file to be written out of the sandbox to their own Firefox profile folder, no matter what their profile folder is named or where it's located.
----
Firefox cookies:
The Firefox cookies files are independent of the cache files. You can have Firefox set to delete or not delete the cache files on exit, and it will not affect cookies.

The cache files for sandboxed Firefox are already being deleted when you exit Firefox. That's because Firefox normally saves its cache files (outside of the sandbox) at a path like:
C:\Users\(user)\AppData\Local\Mozilla Firefox\Profiles\xxxxxxxx.Default\Cache
But none of Sandboxie's templates allow files to be saved out of the sandbox to that location, including the template that allows 'direct access to the entire Firefox profile folder'.

So, all new cache files that are created when sandboxed Firefox runs are already being deleted when the sandbox contents are deleted, unless you have gone out of your way to create your own setting that will allow the cache files to be saved out of the sandbox.
The cache files that are already saved outside of the sandbox will not be deleted unless you tell UN-sandboxed Firefox to delete them on exit.

I have Firefox set to delete active logons and history on exit, and I don't lose any passwords or cookies.
----
Firefox (anti-)Phishing:
A new SafeBrowsing folder is used for the latest Firefox versions.
If you are using the Sandboxie beta versions, you don't need to do anything except confirm that the Firefox Phishing template is enabled for your sandbox.

If you use Sandboxie 3.76 and the latest Firefox versions, then the SafeBrowsing folder would have to be added to the settings for each sandbox where Firefox is used:
Sandbox Settings > Resource Access > File Access > Direct Access
"Add Program" button: firefox.exe
"Edit/Add" button: *\safebrowsing\*
OK

Those like me, who have Firefox profile folders that are not underneath the %UserProfile% folder, or (likely) anyone who uses a portable Firefox install, will have to create their own setting to allow the anti-phishing files to be saved out of the sandbox to the "SafeBrowsing" folder - since tzuk revised the phishing template to include %UserProfile% in the path to those files.

[Baldape]

Thanks Guest10 you always come SDC is able to saving the white list data outside SBIE.
But I did notice one thing even if I configure Firefox to automatically clear active log-ins after I close it certain sites like YouTube/Google or Netflix that I'm still logged in once I reopen FF is there a way to make sure FF clears/logs me off all sites when I close it?

[Guest10]

I believe that what you are asking about, is due to the cookies for those sites logging you in automatically each visit. As far as I know, you would have to turn off the auto-login feature, and the site's cookies would no longer be set to log you in.
Or, have the cookies for those sites deleted after each visit, if SDC can do that;
Or, add those sites' cookies to "Allow for Session", in Firefox Tools > Options > Privacy tab > Exceptions button, so that Firefox will delete those cookies each time that it exits.

[Baldape]

I believe that what you are asking about, is due to the cookies for those sites logging you in automatically each visit. As far as I know, you would have to turn off the auto-login feature, and the site's cookies would no longer be set to log you in.
Or, have the cookies for those sites deleted after each visit, if SDC can do that;
Or, add those sites' cookies to "Allow for Session", in Firefox Tools > Options > Privacy tab > Exceptions button, so that Firefox will delete those cookies each time that it exits.

Of course silly me I've always noticed the exceptions button just never gave it much forethought
Same goes for goes the stay logged-in option for some odd reason I just ignored it.
Thanks Guest10

Why is it always the small things that allude us?