I've got the new beta build of Chrome with extension support - 4.0.249.30, and I have allowed access to the whole '%Local AppData%\Google\*' directory (profile, Gears, etc). When I try to install an extension I get a 'Could not create directory for unzipping.' error. The resource access monitor doesn't show anything interesting. Can anyone reproduce?

Win7 Pro 32-bit
Sandboxie 3.42

Yep I get the same error even when experimenting with extensions whilst having the direct access enabled.
Question though... Is there any way -- (tht envolves simply editing the preference/localstate file) -- to make chrome stop updating its profile everytime its run in the sandbox? Its a little inconvenient to manually change the settings to the ones i selected outside the sandbox everytime. Even the favorites are lost after every subsequent startup, unless I leave the direct access option always enabled - which Im kinda worried to do, since you advised against it for the whole firefox profile folder...

Tzuk can you please add the chrome favorites file to quick recovery?

I added some Google Chrome settings in version 3.42. Have you not noticed that, or are those settings not enough?



Alright, I'll check it out, as soon as I can.

[quote=tzuk]I added some Google Chrome settings in version 3.42. Have you not noticed that, or are those settings not enough?
[/quote]

Yes I have seen the new settings, however I was hoping that there be 2 options for the fav files like IE; direct access or quick/immediate recovery - which is my preffered way. If its such an annoyance I'll understand, but it would definitely make usage a tad easier. It would be great if you could facilitate as many options for chrome as there are for IE, as its becoming quite popular

I don't think you can say it's going to make it easier with no qualifications. Google Chrome, like Firefox and unlike IE, stores bookmarks in a single file. So Quick Recovery in this case would overwrite all the bookmarks outside the sandbox, possibly disappointing those who have been bookmarking stuff both inside and outside the sandbox over some time.

Ok, now I see why its not possible to have this... Thanks for explaining this to me Tzuk.

hello,

Installing add-on on the new Chrome Beta is fast and stable in general.

while running Chrome in sandboxie (with all of '+' definitions - access to everything)
cause a problem: "cannot create a directory..."

Does anyone knows how to run Chrome Beta inside sandboxie,
with an option to install add-on during the running. (win xp 32bit)


Thanks,
Ron

This should be fixed in version 3.43.07.

While installation extensions, Google Chrome launches an instance of its own chrome.exe program in "extension installer" mode. This Chrome sandboxing on this instance conflicts with the way Sandboxie works.

It seems the conflict is the result of Sandboxie causing the program to access C:\SANDBOX folders, and the Chrome sandboxing does not recognize these folders as permitted locations.

So in version 3.43.07, Sandboxie causes the "extension installer" instance of Chrome to run without Chrome sandboxing. Obviously there is still Sandboxie sandboxing on that program instance.

Man am I glad wraithdu created this thread!
I've been testing every build of Chrome (Dev builds or Nightly Chromium builds) since the project was first started. Well I never had any problems getting it to install sandboxed, but ever since Chrome added extension support long ago, I have always had the same "Cannot create directory for unzipping" error with a sandboxed Chrome.

Well I can now confirm 3.43.07 fixes that problem!
Thank you tzuk for the quick fix as usual and keep up the good work!