hi all,
I want to increase my system safety utilizing sandboxie. Can I put all my temp-folders by default into sandboxie folder?
i.e. like:
C:\Users\user\AppData\Local\Temp -> C:\Sandbox\user\DefaultBox\drive\C
C:\Users\user\AppData\LocalLow\Microsoft\ -> C:\Sandbox\user\DefaultBox\drive\C
C:\Users\user\AppData\LocalLow\Microsoft\Internet Explorer -> C:\Sandbox\user\DefaultBox\drive\C
C:\Users\user\AppData\Local\Microsoft\Internet Explorer -> C:\Sandbox\user\DefaultBox\drive\C
C:\Users\user\AppData\Local\Mozilla\Firefox\Profiles\user.default\ -> C:\Sandbox\user\DefaultBox\drive\C
Will that work out for me?
thx
on the safety trip
From the viewpoint of programs that are running sandboxed, those folders are already redirected into the sandbox.
A sandboxed program will read the files from those folders (outside of the sandbox), if the file does not exist inside of the sandbox.
Any changes the sandboxed program makes to the files though, will be written inside of the sandbox.
As far as redirecting those folders for unsandboxed programs, that would seem to imply that you were thinking of a way that will allow you to run programs unsandboxed and yet save the files, in those particular folders, inside of a sandbox.
I'm not sure about the usage of folders 2, 3, and 4 as listed above.
Redirecting the user's "Temp" folder into a sandbox would require redefining the "Temp" environmental variable, on my XP system.
A sandboxed program would also make use of that new variable's description, and it seems to me that it might lead to some long path lengths inside of any sandbox, whenever a sandboxed program tried to store something inside the user's Temp folder.
The sandboxed program might not see that, but Windows might see a long absolute path to the files.
As far as the Firefox profile folder is concerned, it's already redirected into the sandbox when Firefox is running sandboxed.
Again, this would seem to imply that you wanted to run Firefox unsandboxed, instead of sandboxed, and yet use profile folder files that are stored in a sandbox.
Redirecting an unsandboxed Firefox so that it uses a profile folder that's inside of a sandbox doesn't seem very useful, since one advantage of using Sandboxie is to delete the contents of the sandbox, and any malware that might have been picked up.
Deleting the sandbox contents would also delete the profile folder and its files.
I'm sure that you aren't planning to do this, since any malware that you picked up would be stored outside of the sandbox, unless it was saved inside of the profile folder.
If a sandboxed Firefox was to access the profile folder files from that location, it seems to me that any attempted modifications to those files might result in a doubling of the absolute path length to the files as far as Windows is concerned, since the modified files are also saved inside of the sandbox.
If all you want is to redirect the Internet cache files for a sandboxed Firefox, so that they are trapped inside of the sandbox, then that is already the default action.
Have Firefox delete the old cache files while unsandboxed, and from then on running Firefox sandboxed insures that newly created cache files will not leave the sandbox.
They are deleted when the sandbox contents are deleted.
A sandboxed program will read the files from those folders (outside of the sandbox), if the file does not exist inside of the sandbox.
Any changes the sandboxed program makes to the files though, will be written inside of the sandbox.
As far as redirecting those folders for unsandboxed programs, that would seem to imply that you were thinking of a way that will allow you to run programs unsandboxed and yet save the files, in those particular folders, inside of a sandbox.
I'm not sure about the usage of folders 2, 3, and 4 as listed above.
Redirecting the user's "Temp" folder into a sandbox would require redefining the "Temp" environmental variable, on my XP system.
A sandboxed program would also make use of that new variable's description, and it seems to me that it might lead to some long path lengths inside of any sandbox, whenever a sandboxed program tried to store something inside the user's Temp folder.
The sandboxed program might not see that, but Windows might see a long absolute path to the files.
As far as the Firefox profile folder is concerned, it's already redirected into the sandbox when Firefox is running sandboxed.
Again, this would seem to imply that you wanted to run Firefox unsandboxed, instead of sandboxed, and yet use profile folder files that are stored in a sandbox.
Redirecting an unsandboxed Firefox so that it uses a profile folder that's inside of a sandbox doesn't seem very useful, since one advantage of using Sandboxie is to delete the contents of the sandbox, and any malware that might have been picked up.
Deleting the sandbox contents would also delete the profile folder and its files.
I'm sure that you aren't planning to do this, since any malware that you picked up would be stored outside of the sandbox, unless it was saved inside of the profile folder.
If a sandboxed Firefox was to access the profile folder files from that location, it seems to me that any attempted modifications to those files might result in a doubling of the absolute path length to the files as far as Windows is concerned, since the modified files are also saved inside of the sandbox.
If all you want is to redirect the Internet cache files for a sandboxed Firefox, so that they are trapped inside of the sandbox, then that is already the default action.
Have Firefox delete the old cache files while unsandboxed, and from then on running Firefox sandboxed insures that newly created cache files will not leave the sandbox.
They are deleted when the sandbox contents are deleted.
Paul
Win 10 Home 64-bit (w/admin rights) - Zone Alarm Pro Firewall, MalwareBytes Premium A/V, Cyberfox, Thunderbird
Sandboxie user since March 2007
Win 10 Home 64-bit (w/admin rights) - Zone Alarm Pro Firewall, MalwareBytes Premium A/V, Cyberfox, Thunderbird
Sandboxie user since March 2007
Who is online
Users browsing this forum: No registered users and 0 guests