Dun 0 Posted October 22, 2022 Share Posted October 22, 2022 Sandboxie-Plus 1.2.0 introduced new feature: "Use a Sandboxie login instead of an anonymous token". However, enabling it prevents HTTPS websites loading. Further explanations how "Use a Sandboxie login instead of an anonymous token" works:https://github.com/sandboxie-plus/Sandboxie/discussions/2064 Sandboxie developer DavidXanatos asked to create a thread there asking ESET developers to look at the issue. He suggested that there might be an old workaround applied on your security software for the old Sandboxie versions:https://github.com/sandboxie-plus/Sandboxie/issues/2025#issuecomment-1196343325 Original issue posted on the open-source Sandboxie repository:https://github.com/sandboxie-plus/Sandboxie/issues/2025 Requirements to reproduce the issue: - Operating system: Windows 11 22H2 // Windows 10 Enterprise LTSC 2021 x64 (21H2) (10.0.19044.1806) - Sandboxie Plus 1.4.2 // 1.2.0 x64 - ESET Endpoint Security 9.1.2060.0 // Eset Internet Security 15.2.11.0 x64 - Firefox 102.4.0esr x64 // Microsoft Edge 106.0.1370.52 x64 Firefox shows PR_END_OF_FILE_ERROR, Microsoft Edge ERR_CONNECTION_CLOSED error Steps to reproduce: 1) Install Firefox, Edge, Sandboxie 1.2.0 or newer, ESET and make sure SSL scanning is enabled. Firefox download: https://www.mozilla.org/en-US/firefox/enterprise/#download Microsoft Edge download: https://www.microsoft.com/en-us/edge/business/download?form=MA13FJ Sandboxie download: https://github.com/sandboxie-plus/Sandboxie/releases/ 2) Run Edge/Firefox in any sandbox and visit any HTTPS webpage to confirm it will load correctly 3) Close all sandboxed apps 4) Run Sandman -> Options -> Global settings -> Advanced config -> Enable 'Use a Sandboxie login instead of an anonymous token' 5) Run Edge/Firefox in any sandbox and visit any HTTPS webpage to confirm it will NOT load correctly Due to this incompatibility issue, since Sandboxie versions 1.2.7 the "Use a Sandboxie login instead of an anonymous token" is disabled by default. Link to comment Share on other sites More sharing options...
Dun 0 Posted October 22, 2022 Author Share Posted October 22, 2022 I created new discussion on Sandboxie Github https://github.com/sandboxie-plus/Sandboxie/discussions/2383 as well Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted October 22, 2022 Administrators Share Posted October 22, 2022 I was unable to make it work with or without the above mentioned setting enabled and ESET registered or unregistered as a Windows Filtering Platform filter. All I was seeing were some crashes upon launching Firefox: PID 10624: SBIE2336 Error in GUI server: [55 / C0000155] PID 10624: SBIE2335 Initialization failed for process WerFault.exe [88 / 0] I recommend that the developers of Sandboxie open a support ticket and get in touch with ESET developers for further collaboration on a resolution. Link to comment Share on other sites More sharing options...
Dun 0 Posted October 22, 2022 Author Share Posted October 22, 2022 It is not very unusual to have issues with latest version of web browsers running in sandbox. That is one of the reasons why I mentioned Firefox ESR and sandboxie 1.4.2 (currently next to last SBIE version) Link to comment Share on other sites More sharing options...
Recommended Posts