AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Tor browser windows 8.1 64 bits1/30/2024 ![]() GeKo: i suspect the problem is that we use a different compiler for windows binaries than mozilla by default Isaak654: indeed, the last working Tor Browser release with Sandboxie is win64-8.0a8 (released in 2018), so I think it's time starting to find an interested developer GeKo: investigating that is likely to be non-trivial GeKo: providing a patch would be much appreciated Isaak654: Sandboxie developer already looked at it, and he states it's something you need to fix about content sandboxing in 圆4 builds Tor: - Sandboxie software compatibility bug + a crash report ![]() In short, this Sandboxie crash also applies to other Firefox 圆4 builds that use the same non-official toolchain, so it can't be considered a specific Tor Browser issue anymore: #tor channel support about the Sandboxie crash report Tor 64 asked for help on the #tor IRC channel, so I have new interesting findings for this issue. The difference between 32 bit and 64 bit seems to be another Process Injection "Allocates virtual memory in a remote process" and Query Registry "Queries sensitive IE security settings and Reads the windows installation date"ĭoes Sandboxie support process injection? It's a lot of data, I didn't do the logs, you said before that disabling the hooking works but then crashes, with the "Open" configured it doesn't crash? On the other hand an installation of tor 64 bit will simply not start error 0xc00005 if I remember well ![]() Also, at the time of installation it asks me to enlarge the sandbox for xul.dll to more than 10000 but if I do it afterwards it will do the same for a video on the VLC software but it doesn't work afterwards. I also tested a 32 bit Tor installation and it works but only half in the chosen language. I think I saw a program dllhost.exe running in the sandbox while before no I do not know if the Open represents a risk I noticed that it asks me more the file chains to recover. I haven't been able to use OpenClsid, so I'm not sure what it's for and how to make it work. Tor 32 bit seems to work much better with Openfilepath and Openpipepath, OpenKeypath, OpenLpcPath, OpenWinClass. If you set MOZ_DISABLE_CONTENT_SANDBOX=1 as an environment variable that disables the Firefox sandbox and than you can start it. Please complain with them to fix whatever they broke. Well enough time wasted, since Sbie works fine with original firefoxes and since the behavior observed does not seam to be a intentional mitigation, but rather a failure of the hooking mechanism during the image loading stage, the ball is imho on the to dev's side. When I do the same with a original firefox it runs and does not crash. Unfortunately it randomly crashes a minute or two later. The SbieDll.dll loads just fine, but than it crashes some ware else, apparently the ntdll hooks are somehow not properly functional, when I prevent the hooking of all ntdll functions it starts fine, it even loads websites ok, When I prevent the hooking of NtOpenFile NtQueryAttributesFile and NtQueryFullAttributesFile SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002 MsgId: 14 - SandboxieRpcSs.exe īut I don't find the versions they offer fro download: Īlso strangely a similar official Mozilla 64 bit version works just fine. SBIE2203 Failed to communicate with the service Sandboxie: request C0000037 SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002 MsgId: 6 - firefox.exe SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002 MsgId: 15 - firefox.exe X.Org 1.0 or higher (1.SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002 MsgId: 13 - firefox.exe Įrr=41020897.Firefox will not run at all without the following libraries or packages:. ![]() Please note that GNU/Linux distributors may provide packages for your distribution which have different requirements.
0 Comments
Read More
Leave a Reply. |