sandbox part

[Hermite15]

are you saying that if i have ie set to always run sandboxed and i download a file i must manually download it to the sandboxed folder?

NO >>> what I'm saying is that the automatic sandboxing of downloaded files in Internet Explorer cannot work because there's no automatically pre-defined location for the downloads set in Internet Explorer settings. While there is in Firefox.

[bri]

anything downloaded through ie is not auto sandboxed right??

[Hermite15]

anything downloaded through ie is not auto sandboxed right??

right, again because with IE downloads locations are chosen manually each time (for security reasons, which is funny for IE). How do you want to sandbox a download when you choose the download location yourself? 

[bri]

thats not good,you keep saying because of ie but sandboxie has no trouble dealing with ie and downloads.

[pk]

Thanks for this topic. There's really a bug about downloads detection in the latest version; during rewriting hooking functions I've forgot for one check. So, in this avast build all downloaded files (saved by standard legitimate way) are not saved in the sandbox (which is done by default). All files created/downloaded with different ways are always virtualized, this remains.

Just to be clear: if the mentioned checkbox is checked, it does the following:
- changing your browser's settings becomes permanent
- bookmarks/cookies/history/... are saved on disk
- standard downloads are detected and the files are saved on disk outside the sandbox (this works for all browsers, even if you choose different location - so IE downloaded are detected as well; in fact, this also works for other applications than browsers, run e.g. Microsoft Paint and images will be stored outside sandbox as well)

[Lisandro]

Just to be clear: if the mentioned checkbox is checked, it does the following:
- changing your browser's settings becomes permanent
- bookmarks/cookies/history/... are saved on disk
- standard downloads are detected and the files are saved on disk outside the sandbox (this works for all browsers, even if you choose different location - so IE downloaded are detected as well; in fact, this also works for other applications than browsers, run e.g. Microsoft Paint and images will be stored outside sandbox as well)

What happens with addons updates?

[pk]

What happens with addons updates?

Support for addons are not implemented yet, because it's not so easy: when you update addons/extensions, quite lot of files are changed (at least in FF browser). These changes can't be covered by some exception records and therefore we'll add more settings into GUI.

[Lisandro]

Thanks pk.

[Sesame]

This is bit off topic but I was taught that I shouldn't use the phrase like below.

all downloaded files (saved by standard legitimate way) are not saved in the sandbox (which is done by default).

For this sentence can be interpreted in two ways:
1. any downloaded file (saved by standard legitimate way) is not saved in the sandbox (which is done by default). /no downloaded files (saved by standard legitimate way) are saved in the sandbox (which is done by default).
2. not all downloaded files (saved by standard legitimate way) are saved in the sandbox (which is done by default).  e.g.  All that glitters is not gold.

In any case, according to what pk wrote, I guess the first sentence is what he means here.  In any case, the core problem here is that I couldn't figure out how the sandbox is supposed to work during my beta-testing stage.   

[Erroneus]

I'm missing some more info about this sandbox mode. A wiki, knowledge base or even forum thread would be nice.

It would be nice with some examples how to setup up proper sandbox mode for popular programs and what programs would be recommended to run sandboxed.

This sandbox feature seems to be a great product, but it feels a bit rough around the edges.

[bri]

pk you mention a bug in this build.is the way the sandbox handles ie downloads going to be fixed or will it remain this way?i think if ie is runnin sandboxed then any download should not be saved to the real disc.

Thanks for this topic. There's really a bug about downloads detection in the latest version; during rewriting hooking functions I've forgot for one check. So, in this avast build all downloaded files (saved by standard legitimate way) are not saved in the sandbox (which is done by default). All files created/downloaded with different ways are always virtualized, this remains.

Just to be clear: if the mentioned checkbox is checked, it does the following:
- changing your browser's settings becomes permanent
- bookmarks/cookies/history/... are saved on disk
- standard downloads are detected and the files are saved on disk outside the sandbox (this works for all browsers, even if you choose different location - so IE downloaded are detected as well; in fact, this also works for other applications than browsers, run e.g. Microsoft Paint and images will be stored outside sandbox as well)

[pk]

it's intended to work this way:
- if checkbox is checked: all files you download in browser are stored outside sandbox; if browsers use predefined download locations (FF/Opera/...) then these locations are excluded automatically from the sandbox; if you save a file to the own location (mainly IE) then it'll be saved outside the sandbox; this feature also works for other applications than browsers (e.g. MS Office, ...)
- if checkbox is unchecked: all downloads are stored in the sandbox

The checkbox controls only downloaded files, all other files created by a virtualized application are saved in the sandbox. The actual build saves all downloads outside the sandbox.

[bri]

if its intended to work this way for ie whats the point in sandboxing ie when anything downloaded through it is not sandboxed?by the way i uncheck the ais setting(safe location and exclude)and it still saves the file to the real disc and i can install it with no problem,is it supposed to be this way?

[Sesame]

it's intended to work this way:
- if checkbox is checked: all files you download in browser are stored outside sandbox; if browsers use predefined download locations (FF/Opera/...) then these locations are excluded automatically from the sandbox; if you save a file to the own location (mainly IE) then it'll be saved outside the sandbox; this feature also works for other applications than browsers (e.g. MS Office, ...)
- if checkbox is unchecked: all downloads are stored in the sandbox

The checkbox controls only downloaded files, all other files created by a virtualized application are saved in the sandbox. The actual build saves all downloads outside the sandbox.

Thanks, pk for the clarification.

if its intended to work this way for ie whats the point in sandboxing ie when anything downloaded through it is not sandboxed?by the way i uncheck the ais setting(safe location and exclude)and it still saves the file to the real disc and i can install it with no problem,is it supposed to be this way?

  I thought my notebook, which I used for my beta-testing, couldn't cope with the firewall and sandbox functions since I felt they were not mature yet when Avast released them as non-beta versions.  In fact, judging from some reviews and votes in third party sites, quite many people seem to be happy with them.  Probably, we just belong to those unlucky users...

[bri]

i think its ridiculous that when ie is sandboxed and i have the settings for downloads for safe location unchecked it still saves it to the system and can be installed.it is unuseable imo.my families pc found out the hard way (infected).