Sandboxie Support

[.02] Sandboxed Right click> sendTo> CustomBatchScript

2013-02-25T15:25:22-04:00

This problem should be fixed in version 4.01.02.

Related topic:
http://www.sandboxie.com/phpbb/viewtopic.php?t=14388

Statistics: Posted by tzuk — Mon Feb 25, 2013 2:25 pm

[.02] Sandboxed Right click> sendTo> CustomBatchScript

2013-01-29T06:27:53-04:00

And default settings must be what you advise. Thanks!

Also thanks for checking into the issue.

Statistics: Posted by PiwPi — Tue Jan 29, 2013 5:27 am

[.02] Sandboxed Right click> sendTo> CustomBatchScript

2013-01-29T06:06:49-04:00

I can see the problem for a filename with a space. I'll check into it.

As for Drop Rights: Just to be clear. On 64-bit systems without experimental protection, Drop Rights is enabled by default because some other security mechanisms are missing. When experimental protection is enabled, and those security mechanisms are in effect, then Drop Rights is no longer a default setting when creating a new sandbox. In version 4, there is no experimental protection, and Drop Rights is not a default setting.

Statistics: Posted by tzuk — Tue Jan 29, 2013 5:06 am

[.02] Sandboxed Right click> sendTo> CustomBatchScript

2013-01-28T14:21:56-04:00

I tried it again and that's right.

Then I tried it on a file with a space in its name, and that reproduced my issue properly. Even if I do

CODE:

echo "%1"pause

Maybe Sandboxie internals strip the "" or something ? Unless I'm doing something wrong, but that would be odd...

PS: I bet you answered this question a billion times, but what I found here and there on the topic didn't fully address my interrogations. So instead of going into detail I'll just ask it this way: With all your knowledge on Sandboxie internals, configuration and trusted programs exceptions, do you advise to untick the "drop rights" box in Windows 7 64 bit when Experimental protection is on ? You can just go yes/no if you want, that would be helpful already. Thanks a ton

Statistics: Posted by PiwPi — Mon Jan 28, 2013 1:21 pm

[.02] Sandboxed Right click> sendTo> CustomBatchScript

2013-01-28T13:11:15-04:00

I might not understand the problem description but it seems to work correctly for me.

I created this batch file xx.bat in the SendTo folder:

CODE:

echo %1pause

Then I started Windows Explorer under Sandboxie, went to the desktop folder, right-clicked on some file and selected SendTo > xx and it everything worked as expected.

Statistics: Posted by tzuk — Mon Jan 28, 2013 12:11 pm

[.02] Sandboxed Right click> sendTo> CustomBatchScript

2013-01-27T18:58:15-04:00

Hi,

I'm using Sandboxie 3.76 on Windows 7 64 bit, with experimental protection turned on. Admin rights are not dropped. (By the way is it really safe not to drop them on 64-bit with experimental protection ?)

When called from a sandboxed explorer right click > sendTo > shortcutToBatch, a custom batch script created in the real system doesn't get its arguments. Only when the batch has an actual copy inside the sandbox does it work as expected.

If the batch is "echo %1", the cmd.exe window says the syntax is incorrect for the file or folder or volume name.
If the batch is "echo yay", the command window echoes yay properly.

It works outside of a Sandbox.
To make a custom sendTo I just dropped a shortcut in C:\Users\[UserName]\AppData\Roaming\Microsoft\Windows\SendTo. The batch file itself is located in D, Sandboxie is installed in D: and its sandboxes are in a D:\Sandboxes folder.

See this thread for more information.

Thanks if you can help!

Statistics: Posted by PiwPi — Sun Jan 27, 2013 5:58 pm