Sandboxie Support

I have posted the dir c: problem in the SVS board lets wait what they say.
EDIT: While looking across their board i found a beta version 2.1 beta 1.6 that seems to have solved the problem with dir c:

So in the next release exes inside the SB wont be longer able to use Open*Paths, cool

Owen

I haven't read all previous pages so I may ask something already answered, so let me apologies right away for it. When I remember correctly the problem here with the older versions of SB was that the driver couldn't be unloaded once it is in the system because it hooked the SSDT, as the new version ...

TrueCrypt used in portable mode have to install a driver when started, this is blocked by sandboxie for obvious reasons,
however you can enable it
by
BlockDrivers=n
and you may need:
OpenKeyPath=truecrypt.exe,HKEY_LOCAL_MACHINE\System\*
but I'm not sure about the second.

Owen

emmm, ok I havn't tested this enough, dir works indeed, but anyway "cd.." don't I can't change to uper directory mo mather if open path is * or not. The problem seems to be in paths below the sandbox root directory and above the directoris inside current, current>cd desktop and than current\desktop>...

What about point 1. the not accessibility of sanadbox paths like ...\Sandbox\???\user\current> it would be cool when the path "...\Sandbox\???\" would be handled as openfilepath instad of no access. This way the recovery app could check if the current file is really sandboxed or not. The next evolut...

when I specify OpenFilePath=cmd.exe,* But why do you specify this? hehe, of cause to see how well SB work ;) I was looking for a possibility to unsandbox files with an app that is inside, a further thought would be to make an small app or script that have the rights do do so and that will unsandbox...

Hi I have some more problems to report: 1. when I open cmd.exe in sandbox it is started in ...\Sandbox\???\user\current> but this folders are not accessible, the working directory should be set to some valid folder. 2. when I specify OpenFilePath=cmd.exe,* and go to a folder where i have some sandbo...

hehe... I know this feature... and I realy don't like it, this way a lot of data leeks into your system, data that you may want to be destroy for all eternity once you pull the plug of your PC. OT: I use an TC_Temp drive to store a sandbox called [Temp], the drive is Twofish encrypted with an random...

How will you know what number represents what sandbox?
Make if [#ID] where you can set the ID for evenr SB to an arbitrary srting in the sb.ini and I'm in and if ID is not set than only [#] will be shown.

Owen

Yes that's it and it even works, but:
there is a bug in the guide:

[GlobalSettings]
FileRootPath=C:\Sandbox\MySandbox

same for IPC and Key.


ps:
KeyTrace it says "a" and "d" are alowed, but what about "i"? "i" should also be valid for registry keys?



Owen

I would like the ability to specify obtionaly alternative folders for particular sandboxed, something simmilar to "BoxRootFolder" but available for every particular sandbox lets call it "BoxFolder".

Owen

try the trace obtions PipeTrace=d IpcTrace=d and use Dbgview.exe from sys internals with *SBIE* as filter Than you will see what resources are blocked and than you can open it for the apriopriet processes. PS: I don't have distiller installed in ma setup so i dont have an ad hock solution, sry. Owen

Try:
OpenFilePath=Acrobat.exe,\Device\NamedPipe\Adobe LM Service0ECA17E3-C1AE-4b96-89EF-8F8F0D78AF81

Owen

Sry for the other thread,

about the problem, if i get it right the problem occured when FF uses filemove than when the source file was sb'xed the target was to even if the particular path is open.

Is it now fixed in generally, or only for FF?

Owen

how about making the "temporarily disable" switch ask the user for how long it should be dissabled,
for 1 action
for 1 minute
for 10 minutes
for ever (untill you uncheck the dissable obtion manualy)

Owen