Trust No Program
This topic is locked: you cannot edit posts or make replies.
tzuk


Joined: 22 Jun 2004
Posts: 15159
Reply with quote
Version 3.43.17 should resolve the crash in QTracker. As for

tzuk wrote:
I probably can't reproduce this specific thing, because it involves specific DVD hardware. But I will try to access hard disk devices directly, killdisk-style, and see if Sandboxie blocks this access or not.


I did test this and there is protection on direct device access to hard drives. However I recall that some versions ago I changed the treatment of CD and DVD devices to allow direct device access. Perhaps your DVD firmware is accessed/manipulated by special I/O control codes sent out to the device.

_________________
tzuk
View user's profileSend private message
QAZ
Guest

Reply with quote
so does this mean that executables can access dvd drives, circumventing the sandboxie control? or that you have them covered?
tzuk


Joined: 22 Jun 2004
Posts: 15159
Reply with quote
Direct device access means there is no Sandboxie protection on accessing the device. If you're concerned, you can add the drive in Sandbox Settings > Resource Access > File Access > Read-Only Access or even Blocked Access.
View user's profileSend private message
QAZ
Guest

Reply with quote
Thanks for the tips Tzuk, however could you plz consider adding access restrictions to these devices as was in the past versions?
tzuk


Joined: 22 Jun 2004
Posts: 15159
Reply with quote
There were several occasions where people tried to run their games in Sandboxie, but protection on the CD/DVD drives was causing the copy-protection to fail. So for now I'm going to leave it like this, for now.
View user's profileSend private message
QAZ
Guest

Reply with quote
Ok I've got an idea.. If its not much hassle for you, could you then create a SBIE control option that enables such protection at will for people that need it?

Should the closed filepath provide the same protection as was formerly implemented?
Julian


Joined: 09 Aug 2009
Posts: 174
Reply with quote
tzuk wrote:
Version 3.43.17 should resolve the crash in QTracker.

Indeed, I can confirm this. Thanks Smile

The DVD burner flasher issue is done for me after your explanation. I don't think that this is critical and paranoids can modify their configuration if they want to do so.

Of the remaining issues here in this thread, IMO the problem with the foobar2000 installer should get the highest priority. It's a "real world" bug.
Nevertheless it would be nice if the other things could get fixed at a later point of time too. Wink
If you have questions regarding details how to reproduce etc, please ask them.
View user's profileSend private message
tzuk


Joined: 22 Jun 2004
Posts: 15159
Reply with quote
QAZ, the Blocked Access (or ClosedFilePath) is going to completely block all access to the device, much better for you than what was formerly implemented.

Julian, I did try foobar2000 briefly, however my recollection is that I didn't see any means to update it. So I will take you up on your offer, please explain how I can reproduce.
View user's profileSend private message
Julian


Joined: 09 Aug 2009
Posts: 174
Reply with quote
tzuk wrote:

Julian, I did try foobar2000 briefly, however my recollection is that I didn't see any means to update it. So I will take you up on your offer, please explain how I can reproduce.

Sorry, I have been a bit mistaken. I just need to install foobar2000 into the sandbox and during the installation infinite regsvr32.exes are getting started.

I noticed that first when foobar2000 1.0 came out and I wanted to install it sandboxed because I didn't like the previous betas. I had still foobar 9.x installed, that's why I thought it would only happen at update installations. But now I've just retested in a VM. It also happens when you just install foobar into the sandbox without the need of having an old foobar installation on the real system.
View user's profileSend private message
nick s


Joined: 20 Dec 2008
Posts: 331
Reply with quote
The sandboxed foobar2000 1.0 install hangs at...

Quote:
Execute: "C:\Windows\system32\regsvr32.exe" /s "C:\Program Files (x86)\foobar2000\ShellExt64.dll"

It may or may not be related, but when I terminate the hung install (using Terminate Programs), I get the following message...

Quote:
SBIE2399 Service 'RPCSS' fails with error 1066. Last checkpoint was 0

_________________
Nick
View user's profileSend private message
Julian


Joined: 09 Aug 2009
Posts: 174
Reply with quote
Another issue:
I can't install Google Chrome via its webinstaller sandboxed:
http://www.google.com/chrome
After Sandboxie starts BITS the setup process closes.
View user's profileSend private message
tzuk


Joined: 22 Jun 2004
Posts: 15159
Reply with quote
Julian and nick s, thanks for the problem report, Sandboxie 3.43.18 now honors a program's request to temporary disable wow64 filesystem redirection (System32->SysWow64), and it fixes this problem.

I did not see the problem with RPCSS error 1066 in this case, however I've seen this error before. I believe it is related to SandboxieRpcSs starting to shut down, after all programs in the sandbox stop, but if you're quick enough to get a new program started in that short window of time, you'll see this, and other kinds of problems. I will improve this in a future version.

As for Google Chrome, try version 3.43.18.
View user's profileSend private message
Julian


Joined: 09 Aug 2009
Posts: 174
Reply with quote
tzuk wrote:

As for Google Chrome, try version 3.43.18.

The problem is still there. Sad

Back to the flasher issue:
It doesn't help if I add my DVD burner ("E:") to file restrictions (neither read only nor full access). My vague guess is that they don't apply for direct sector access. If I add "\Device\HarddiskVolume2" this happens:


But the foobar problem is gone. Due to that way of how you fix bugs I've bought Sandboxie. Smile
View user's profileSend private message
Julian


Joined: 09 Aug 2009
Posts: 174
Reply with quote
Another observation:
If I start Qtracker sandboxed in compatibility mode for Win XP SP3 the ping option doesn't work again.
View user's profileSend private message
nick s


Joined: 20 Dec 2008
Posts: 331
Reply with quote
tzuk wrote:
Sandboxie 3.43.18 now honors a program's request to temporary disable wow64 filesystem redirection (System32->SysWow64), and it fixes this problem.

foobar2000's install now completes normally. When I try to play MP3s, unfortunately, foobar2000 displays this error: "Unrecoverable playback error: Device not found (0x88780078)".

tzuk wrote:
As for Google Chrome, try version 3.43.18.

Like Julian, the installer still quits for me after the BITS message.
View user's profileSend private message
Several issues with 3.43.14 on Seven x64
You cannot post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT  
Page 2 of 4  

Use the RSS feed to watch this topic for replies
  
  
 This topic is locked: you cannot edit posts or make replies.  

Sandboxie is Copyright © 2004-2012 by Sandboxie Holdings LLC.  All rights reserved.
Sandboxie.com | Contact Author
This site has been viewed 213,193,404 times since June 2004