Open sandboxed if matches xyz file extension

[_is_m00nbl00d]

My suggestion comes in the line of what is suggested here.

Currently, I download files to an unsandboxed folder, where nothing gets execution rights. In this scenario I got no reasons to have this folder sandboxed.
But, I do have different sandboxes for different applications, such as for Adobe Reader. So, if I open a PDF file saved in this folder, it will be opened in the Adobe Reader sandbox.

I do not force Office processes to run sandboxed, though. I run them sandboxed, manually.

What I'd like for Sandboxie to offer is a feature to allow to add certain file extensions to be forced to run in a specified sandbox. For example, I want to force *.doc files to automatically run sandboxed when I double-click them.

What do you guys think, and obviously Tzuk lol ? Worthy to have under consideration for a future release?


Thanks

[tzuk]

For example, I want to force *.doc files to automatically run sandboxed when I double-click them.

Document files [which is anything that is not a .exe or .com] are not programs, and cannot be directly intercepted by Sandboxie. You should force the corresponding program to the sandbox you want. In this case, WINWORD.EXE handles .doc files.

As for clicking documents/programs in a sandbox folder but actually opening them in another sandbox, I don't think I will offer this feature directly. But there have been requests to be able to specify a list of programs to be excluded from running in a sandbox. So you when that feature is available you may be able to specify WINWORD.EXE as excluded in one sandbox, and as a forced program in another sandbox.

[_is_m00nbl00d]

I know a document file is not a program, but I was wondering if Sandboxie could ever work that way, by intercepting the file type and then open the respective process, that actually handles the file, in a specified sandbox.

But, what you mentioned sure is a great feature. Thanks.

[Username]

intercepting the file type

First, it's rather lame approach IMO (although SBIE doesn't really care ATM which file to intercept but its name).
Second, SBIE injects the executable to comply with the restrictions, no mempatching.
Third, could you please define 'opening XYZ file'? Ain't it opening XYZ via some application (executable or plug-in/add-on)?
Fourth... what are you trying to get after all? Because it seems to be a wrong way

[_is_m00nbl00d]

intercepting the file type

First, it's rather lame approach IMO (although SBIE doesn't really care ATM which file to intercept but its name).
Second, SBIE injects the executable to comply with the restrictions, no mempatching.
Third, could you please define 'opening XYZ file'? Ain't it opening XYZ via some application (executable or plug-in/add-on)?
Fourth... what are you trying to get after all? Because it seems to be a wrong way

First - You misunderstood me. I never talked about file names, but rather file types, or simply putting it: extensions (*.exe, *.doc, *.txt, etc).

Second - Correct; which is why I suggested what I suggested (Tzuk mentioning something different is in the making, allowing the same; just a different, and better approach. I just didn't think of it, I guess I just let my imagination flow ;D )

Third - Obviously, when a file type is opened, it is opened by an application/process. Considering I haven't thought of the easy way - what Tzuk mentioned - I let my imagination bring something else.

But, the file is opened by the predefined application. (Unless the user opens the file with some other application.) Considering that, I had in mind Sandboxie could be changed to allow the user to have a sandbox set to open only certain file types stored in a folder, with this folder being forced into the sandbox, but only files matching certain extensions (*.doc, etc) would be opened in this sandbox, while every other wouldn't, despite the whole folder being forced to run sandboxed.

As I explained in my first post, I have folder where I download files to. Nothing in the folder has execution rights. I have other sandboxes where I forced my PDF reader to run in it. When I open a PDF file stored in the downloads folder, it will be forced to open in PDF reader's own sandbox; but, if I force the folder to run sandboxed, then if I open the PDF file, it will be open in this forced folder respective sandbox and not PDF. There's no way to exclude this, which is why I suggested what I suggested. I didn't remember of suggesting the option to exclude processes from sandboxes. lol

[yasuo]

hi there,

just associate the extension with sandboxie's start.exe - it will run the sandbox and the windows "inside" the sandbox will decide wich porogram to start.

Im used this for .pdf and .pps files and it worked fine

blabla.doc => rightclick => open with => c:\...\sandboxie\start.exe or whereever it is

[i@mJONNY]

I tried following the advice here alas couldn't work out what blah.doc and start.exe meant. tried modifying the key created by defaultprograms.exe so .pdf had an 'AcrobatSB' application registered... didn't work.

Tried opening with start.exe... didn't work.

In the end the solution was painfully obvious. Open with acrobat. End of.





so now chromeportable is a universal fileviewer (and default pdf viewer and acrobat is there (sandboxed:) if I'm sifting through war&peace

hope this helps someone!