| Author |
Message |
| Ruhe |
|
 |
| tzuk |
Posted: Sun Sep 26, 2010 7:30 pm Post subject: |
|
| It's not a bad feature request but look, I haven't even added an easy way to set up AutoExec commands. I will probably work on these type of automation utilities at some point but it's not a high priority at this time. |
|
 |
| lwc |
Posted: Sun Sep 26, 2010 7:26 pm Post subject: |
|
| tzuk wrote: |
| Have you considered having scripts that are unrelated to Sandboxie and Delete Command, which you invoke when you wish to save or restore the sandbox? |
I've considered it but I prefer it to be internal. When I get people to install their own Sandboxie, I don't want to also give them my own script. It'll just be confusing. Sandboxie should be standalone. |
|
 |
| tzuk |
Posted: Sun Feb 07, 2010 8:51 pm Post subject: |
|
I thought we were past the PreExec thing.
Have you considered having scripts that are unrelated to Sandboxie and Delete Command, which you invoke when you wish to save or restore the sandbox?
Maybe a couple of shortcuts on your desktop that take care of this. |
|
 |
| lwc |
Posted: Sun Feb 07, 2010 6:31 pm Post subject: |
|
So maybe keep the renaming, but prevent anything else. The question is what is anything else. Is there a list or is it just renaming plus unhiding the LOG file?
Although note that those who save/restore sandboxes (there were a lot of these questions lately) already take the risk. This is because the current method copies over the backup folder, which assumes the destination doesn't exist. This is exactly why "Pre Exec" is more fitting (it wouldn't start the sandbox until it's "ready"). Do you think it'll ever be possible to have such a thing? |
|
 |
| tzuk |
Posted: Sun Feb 07, 2010 12:19 pm Post subject: |
|
I don't think such a feature deserves a GUI element. At this point I believe you'd probably be the only one using it. But I can revise Start.exe so if the Delete Command starts with a special indication, then it would skip the "preparation" process.
But you should take into consideration that if a new sandboxed program is started, while you mirror the contents, and the sandbox folder has not been renamed, then it might mess up your mirroring results. |
|
 |
| lwc |
Posted: Sun Feb 07, 2010 10:54 am Post subject: |
|
Point taken. So "Delete Command" aside, do you plan to eventually enable a standalone facility to do something before the sandbox begins (even if they begin without Start.exe)?
If not, how about a checkbox next to "Delete Command" called "prepare for deletion"? Signaling no would just run the delete command on the regular folder (thus supporting something like Toucan). |
|
 |
| tzuk |
Posted: Sat Feb 06, 2010 9:29 pm Post subject: |
|
You can't just assume that because there is a Delete Command, it must be a trivial task to also have the PreExec you suggest. But I'm afraid that is just not the case. It would be true if all programs went through Start.exe, which begins un-sandboxed and might run a PreExec command, before switching to sandboxed mode. But forced programs completely bypass Start.exe.
On the other hand, Delete Command always works the same, regardless of the way the program started. And AutoExec also works the same way, regardless of the way the program started. |
|
 |
| lwc |
Posted: Fri Feb 05, 2010 8:16 pm Post subject: |
|
I just meant myself on a few computers. I wouldn't want a black screen everytime. It always gives me the feeling of an evil script. Anyway, I have a folder of the latest installation files for all my programs, which I store for backup. If you release a new version, I delete the old installation and put the new one instead. It's more comfortable having just one file for each installation.
Although I did and hopefully will again help people install and set up their own Sandboxie. But if they ask how to save/restore sandboxes, there's no way they'll understand how to use a batch file.
But that's all off-topic. The point is "Pre Exec" would be as helpful as "Delete Command". Since "Delete Command" already exists, it means there's potential support for "Pre Exec". |
|
 |
| tzuk |
Posted: Fri Feb 05, 2010 5:43 pm Post subject: |
|
| lwc, I am not sure where you're going with this. To whom are you distributing (or are you planning to distribute) installations of Sandboxie, who would be intimidated by the black screen? |
|
 |
| lwc |
Posted: Thu Feb 04, 2010 4:40 pm Post subject: |
|
So what I mean is something that runs before the sandbox even starts. Maybe "Pre Exec" would be a better a name for it. It does what it does before Sandboxie even has anything to do with the sandbox. Kind of like the difference between autoexec.bat and Programs=>Startup.
A batch file would mean:
1) An intimidating black screen.
2) It would have to be carried arround with the Sandboxie installation.
BTW, I've noticed Delete Command doesn't support any internal variables except "%sandbox%" (which, as you know, is not the original "%sandbox%"). It also seems to do various minor things like taking the read-only flag off the root folder and unhiding RegHive.LOG. I was thinking to use Toucan - a portable free utlity that mirrors only changes - and then rename the special "%sandbox%" back to its name. Alas, the aforementioened small changes probably mean it's not a good idea. It would have only worked if there was a "Post Exec" command that doesn't necessarily involve deletion. |
|
 |
| tzuk |
Posted: Thu Feb 04, 2010 3:25 pm Post subject: |
|
You can't copy over the reghive files of a sandbox if your program is running in that same sandbox. You will have to use registry import/export commands to populate the sandboxed registry.
I could add %sandbox% for AutoExec processing, but not external AutoExec, because it wouldn't work with forced programs, whereas the current form of AutoExec would work just fine.
Why do you say that a batch file would "never be the same thing" ? |
|
 |
| lwc |
Posted: Thu Feb 04, 2010 2:44 pm Post subject: |
|
I was thinking about this lately because I have a 130 Mb sandbox (which means 260 Mb when resorting to "Delete Command").
You said to use OpenFilePath, but keep in mind I need to copy RegHive & RegHive.LOG. Besides, doesn't Auto Exec only run after they're already created?
Another issue is that environmental variables only work for settings and not for the sandbox itself. So "%Sandbox%" is not useable for Auto Exec.
I just want to copy mysandbox_dummy into mysandbox before mysandbox starts. An external Auto Exec would just be "copy mysandbox_dummy mysandbox". Yes, I realize I can start Sandboxie through a third party (e.g. a batch file), but it'll never be the same thing. If Sandboxie already has the foundation for the external "Delete Command", why not doing the same thing for sandboxes' restarts (i.e. an external "Auto Exec")? |
|
 |
| lwc |
Posted: Wed Mar 05, 2008 12:55 pm Post subject: |
|
It's really not the same to xcopy multiple folders + exporting registry + importing registry as opposed to just use a single (external) command.
In any case, please move this topic into feature request. I've changed the subject of this topic to reflect Sandboxie currently doesn't have such a thing. Thanks. |
|
 |
| tzuk |
Posted: Wed Mar 05, 2008 11:17 am Post subject: |
|
| I already described how to use registry export/import functions to populate the sandboxed registry. As for XCOPY, I really see no reason why it shouldn't work. So as I said earlier, I still don't see a reason to add an unsandboxed AutoExec, just because you are having some small problem with XCOPY that you have not yet resolved. |
|
 |