5.14 Released

[Craig@Invincea]

Ya, It hasn't worked since 2007. This can be found in the forum here http://forums.sandboxie.com/phpBB3/view ... g+and+drop

That was before Invincea took over in late 2013 obviously.

[ssj100]

By the way, I edited my post just before you posted, just for your interest.

Anyway, the link you referenced above seems to regard a different (although similar) issue? tzuk writes: "That's right, you can't drag-and-drop from an unsandboxed app to a sandboxed window", and "...it can't be resolved without compromising the security of the sandbox". So I suppose with that particular mechanism, it would be best not to do any fiddling.

What I thought you were referring to is the scenario where you have a sandboxed windows explorer open. So you're effectively running a sandboxed app (which is explorer.exe in this case) and attempting to drag/drop files (with the mouse) out of this sandboxed process/space, and on to an unsandboxed space. This appears to also be blocked. However, the mechanism of copying/cutting files out of this sandboxed explorer.exe window by using the right-click and keyboard commands seems to have worked all along (except with version 5.12). That's why I was asking whether this was intentional, as I wouldn't be surprised if malware could take advantage of this "vulnerability"?

[ssj100]

For what it's worth, drag/drop seems to work when pulling files from an unsandboxed window to a sandboxed window. But as noted above, it does not work the other way around - that is, from a sandboxed window to an unsandboxed window.

[bo.elam]

For what it's worth, drag/drop seems to work when pulling files from an unsandboxed window to a sandboxed window. But as noted above, it does not work the other way around - that is, from a sandboxed window to an unsandboxed window.

As long as I can remember, what you describe above is the behavior I seen when dragging and dropping files.

Bo

[Craig@Invincea]

Ya, Tom and I debated about this All Thursday...and we both swore we've done it.
We've also tested other things related to Cut/Copy and Paste and drag and drop. Lot of testing old versions, and old OS stuff. Noticed some quirks in XP, that aren't present after XP. It's not a SBIE thing, it's certainly a Windows thing.

Currently, the behavior in 5.13.2 is what is expected and according to what we can gather in old forum posts & Tom looking at the code, etc,.. drag and drop will never be "constant" when working, it's been known to crash.. and as of right now, it's not functional.

[superkryo]

Java installer, e.g. the latest jre-8u91-windows-x64.exe, fails to install on Win10 x64 due to error code 1603. Can't see anything obvious in resource monitor. Version 5.12 works fine.

[Syrinx]

Finally updated to 5.13.2 last night, haven't noticed any new issues though I can't really test the copy/paste fix either as I've never seen the problem.

[ssj100]

Ya, Tom and I debated about this All Thursday...and we both swore we've done it.
We've also tested other things related to Cut/Copy and Paste and drag and drop. Lot of testing old versions, and old OS stuff. Noticed some quirks in XP, that aren't present after XP. It's not a SBIE thing, it's certainly a Windows thing.

Currently, the behavior in 5.13.2 is what is expected and according to what we can gather in old forum posts & Tom looking at the code, etc,.. drag and drop will never be "constant" when working, it's been known to crash.. and as of right now, it's not functional.

Probably best to leave it "not functional" then? I don't hear many (any?) people complaining about the lack of drag/drop functionality.

[ssj100]

Finally updated to 5.13.2 last night, haven't noticed any new issues though I can't really test the copy/paste fix either as I've never seen the problem.

Well, this particular copy/cut/paste problem existed on 5.12 only. And I'm pretty sure only on 64-bit systems. 32-bit systems weren't affected. Presumably you are on 32-bit?

[Craig@Invincea]

It existed before then, Since around beta 5.11.8. As we confirmed that in some internal testing.
32 and 64. And it wasn't all the time, it could be sporadic too.

[Syrinx]

Presumably you are on 32-bit?

Win 7 x64 but I don't do a lot of copy/cut/pasting anyway inside a box. If anything it's usually just copying text/links in or out of the browser.

[ssj100]

It existed before then, Since around beta 5.11.8. As we confirmed that in some internal testing.
32 and 64. And it wasn't all the time, it could be sporadic too.

Interesting, I couldn't reproduce the issue on Windows XP, 32-bit. On Windows 7 and 10 64-bit (VM), the issue was reproduced easily. I'm always more convinced that an issue exists when I can reproduce it in a freshly installed Windows, which is what I test in my VMs (have snapshots of "baseline" versions of these Windows editions). Been too lazy to setup 32-bit Windows 7/10 VMs haha.

Didn't test the beta versions this time, but appreciate that you guys are on to it!

[ssj100]

Presumably you are on 32-bit?

Win 7 x64 but I don't do a lot of copy/cut/pasting anyway inside a box. If anything it's usually just copying text/links in or out of the browser.

The issue was with copying/cutting/pasting actual files (eg. a video file) from a sandboxed explorer window to a unsandboxed window/desktop.

[Healer135]

Please let me submit a remark too. I am far from saying my problem is serious enough for posting it as a separate topic. Anyhow, I suppose the same issue may affect some other programs being sandboxed. I personally utilize Sandboxie to keep my PC clean when running a couple of games (older ones) and a number of applications I do not use regularly. So I have been running an old standalone installation of Gothic 4: Arcania with the very latest patch downloaded just at the time of JoWood bankruptcy. It was claimed it removed DRM after all but it seems still to have been some sort of official. Now as I updated to 5.13, I get a bunch of "SBIE2310 Name buffer is approaching overflow" (a scarcely described error) and the game cannot start. I assume the conflict may be caused by not fully disabled securom remainders or something like that. The point is that it does not work at all with Sandboxie since version 5.12 incl. later betas, and before that (until 5.10) it worked flawlessly. Perhaps, it can it be fixed/managed somehow in newer releases.

[Craig@Invincea]

As for DRM, SBIE wouldn't have anything to do with that, either blocking it or otherwise. So, there could be something else in that game update?
As for that error, more info here : http://www.sandboxie.com/?SBIE2310

As for the game, not something we test.. (not a typical use case for SBIE)...Nor have any of our updates/betas for a long, long time addressed anything specific directly involving games. You can check the complete change logs here http://beta.sandboxie.com

Maybe the update to the program caused an issue? Did you try 5.12/5.10 of SBIE? [ http://www.sandboxie.com/index.php?AllVersions ]
- We've removed most of the older versions..Anything below v5 should not be used, we left the most stable of each just in case someone absolutely needs it, but we do not support those versions directly.. ]

If you're going to run the game under the authority of SBIE (and you've paid money for that program) it's best to install it on your host machine and run it "as sandboxed" if you need to.

Sandboxie, is to protect/isolate you from unknown threats, with some ability to install software directly into the SB. This is more and more in frequent because of many many things and the fact most programs need to interact so closely with the OS.

Remember, SBIE is not a VM. If you need something like that, there are many options out there to use in combination of SBIE.