Sandboxie-Plus v1.11.2

I have a new suggestion to make. First, let me say that I appreciate the new feature of "outsourcing" the box-content to a RAM-Drive very much. It seems by far the best way to leave less traces behind while surfing the web.

There is one throwback though. Depending on various RAM-configurations the space for such a RAM-Drive, although dynamically allocated, will be somewhat limited. As it happens only recently I had to download 2 extra-large files from the net (8 and 10,5 GB each) which did exceed the space my RAM-Drive considerably - and so the download failed after several GBs already transmitted (ok, I could have anticipated this but I'll admit I didn't contemplate much when hitting the DL-button).

So I had to temporarily re-configure my sandbox to run on conventional storage for that purpose.

So the question arises - would it be possible to implement some kind of another "pause-button" for users that currently make use of the RAM-Drive-feature that would allow to re-direct very large files to conventional storage before downloading without having to re-configure the whole sandbox 2 more times (first off the RAM-Drive and then back on again)?

 

Like that idea! Or some other mechanism. Only happened to me on the very odd occasion.

 

Why not open a location with OpenfilePath and save large files there?

 

I also see this issue on my Win7SP1x64(English) with sbie-plus v1.11.2.

 

Good advice, at least for a temporary workaround! Already implemented. TBH I could (and should) have come up with this idea myself. Although for the future it would be even nicer if such a setting could be made conditional upon a threshold file-size as for normal operation it would perhaps be undesirable (out of security concerns) to have every file downloaded to that path "breaking out" of the sandbox on principle, in particular if this were some kind of executable file. As obviously the risk for inadvertently introducing any kind of malware to the system that way is much higher for executable files - while on the other hand extremely large files that might otherwise enforce such a "breakout"-solution (e.g. data- or video-files) - luckily as well as usually - are NOT of the executable kind.