Brett wrote:Does current Firefox use same cookies file while sandboxed and when not sandboxed (shared cookies)
Yes.
The best way to insure that 2 instances of Firefox do not share anything, is to create a second Firefox profile.
They won't share any the same profile files.
They will have separate cookies, bookmarks, extensions, etc.
They can be run simultaneously without interfering with each other.
Both profiles must be maintained though, by updating their extensions separately.
Each of them needs to be run unsandboxed one time, whenever the Firefox program is updated - like the next program update scheduled for next Tuesday (Fx 27).
If firefox.exe is in a "
ProgramFiles" folder (as opposed to "
ProgramFiles(x86)" )
"C:\
Program Files\Mozilla Firefox\firefox.exe" -profilemanager
Starts the profile manager, and you can then Create a new profile.
You could create the new profile on a TrueCrypt volume that's mounted as a drive letter, so all of the profile files are encrypted when the TrueCrypt volume is not mounted.
Profile Manager has the unfortunate tendency to set the new profile as the default profile that Firefox uses when it starts, so after the new profile is created you may want to run the Profile Manager again, select the "default" profile, and then Start Firefox - to set the "default" profile back as the one that Firefox uses if the profile name is not provided on the command line.
To use the new profile without going through Profile Manager each time, create new shortcuts that list the name of the new profile in the Properties > Target box of 2 new shortcuts, as follows.
--
Running Firefox with the new profile, unsandboxed, using a profile named NewProfile.
Substitute the name you give your new profile in place of NewProfile in the command line:
In the shortcut's Properties > Target box:
"C:\
Program Files\Mozilla Firefox\firefox.exe" -no-remote -P "NewProfile"
(The profile name must be listed inside of quotes)
The above is used for purposes of adding/updating the extensions in the profile.
--
To start Firefox sandboxed (using DefaultBox and the Newprofile profile):
"C:\
Program Files\Sandboxie\Start.exe" /box:DefaultBox "C:\
Program Files\Mozilla Firefox\firefox.exe" -no-remote -P "NewProfile"
----
As an alternative you could install a version of Portable Firefox, but the location of it's profile folder would need to be specified in your Sandbox Settings, if you want to use the Sandboxie "Firefox" templates that are provided.
Install the Portable program and create a sandbox, if it doesn't exist.
Then select at least one of the Firefox templates for that sandbox at:
Sandbox Settings > Applications > Web Browser > Firefox
and click OK.
Then:
Sandbox Settings > Applications > Folders
and navigate to and select the profile folder for Portable Firefox.
OK
----
Firefox could be installed inside of a sandbox, but the Firefox install that's outside of the sandbox should be hidden while installing it inside the sandbox. Otherwise, the sandbox install will see the extensions, bookmarks , etc that are in the unsandboxed install.
Installing inside the sandbox means that you can't use Delete Contents to get rid of junk/malware etc without also deleting the Firefox program in the sandbox.