Released Sandboxie Plus (Sbie fork) Versions with Signed Driver

Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by DavidXanatos, Dec 7, 2020.

  1. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    1,006
    Location:
    Viena
    Urgent security fixes (thanks diversenok)

    fix.png
    Build 5.46.0 resolves many box isolation issues some of them critical that could allow rogue applications to escape the sandbox. It is highly advised to upgrade quickly to the new builds. For further details please review the change log below.


    If you have issues with an update installation, just uninstall the previous version keeping the sandboxie.ini and reinstall the new build.


    Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v0.5.4



    ChangeLog
    Added
    • Sandboxie now strips particularly problematic privileges from sandboxed system tokens
      -- with those a process could atempt to bypass the sandbox isolation (thanks Diversenok)
      -- old legacy behavior can be enabled with "StripSystemPrivileges=n" (absolutely NOT Recommended)
    • added new isolation options "ClosePrintSpooler=y" and "OpenSmartCard=n"
      -- those resources are open by default but for a hardened box its desired to close them
    • added print spooler filter to prevent printers from being set up outside the sandbox
      -- the filter can be disabled with "OpenPrintSpooler=y"
    • added overwrite prompt when recovering an already existing file
    • added "StartProgram=", "StartService=" and "AutoExec=" options to the SandMan UI
    • added more compatybility templates (thanks isaak654)
    Changed
    • Changed Emulated SCM behavior, boxed services are no longer by default started as boxed system
      -- use "RunServicesAsSystem=y" to enable the old legacy behavior
      -- Note: sandboxed services with a system token are still sandboxed and restricted
      -- However not granting them a system token in the first place removes possible exploit vectors
      -- Note: this option is not compatible with "ProtectRpcSs=y" and takes precedence!
    • Reworked dynamic IPC port handling
    • Improved Resource Monitor status strings
    Fixed
    • fixed a critical issue that allowed to create processes outside the sandbox (thanks Diversenok)
    • fixed issues with dynamic IPC port handling that allowed to bypass IPC isolation
    • fixed issue with ipc tracing
    • fixed CVE-2019-13502 "\RPC Control\LSARPC_ENDPOINT" is now filtered by the driver (thanks Diversenok)
      -- this allowed some system options to be changed, to disable filtering use "OpenLsaEndpoint=y"
    • fixed hooking issues SBIE2303 with chrome, edge and possibly others
    • fixed failed check for running processes when performing snapshot operations
    • fixed some box option checkboxes were not properly initialized
    • fixed unavailable options are not properly disabled when sandman is not connected to the driver
    • fixed MSI instalelr issue, not being able to create "C:\Config.Msi" folder on windows 20H2
    • added missing localization to generic list commands
    • fixed issue with "iconcache_*" when runngin sandboxed explorer
    • fixed more issues with groups
     
  2. EspressoGuy

    EspressoGuy Registered Member

    Joined:
    May 4, 2020
    Posts:
    18
    Location:
    USA
    @DavidXanatos I am on classic. Has that been updated with the security fixes?
     
  3. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    1,006
    Location:
    Viena
    Plus and Classic have the same core components this means ALL Security fixes as well as ALL Compatibility improvements always apply to booth equaly.
    The used UI has no effect on security, compatibility or performance.
     
  4. diversenok

    diversenok Registered Member

    Joined:
    Oct 7, 2018
    Posts:
    18
    Location:
    Russia / Netherlands
    Also, we advise those users who still use Sophos's release to update to Sandboxie Plus. Note, though, that even the older versions of Sandboxie are still significantly more secure than some other sandboxes (like Cybergenic Shade, for example) due to their architecture.
     
  5. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,918
    Location:
    .
    Thank You!
     
  6. Peter 123

    Peter 123 Registered Member

    Joined:
    Feb 1, 2009
    Posts:
    395
    Location:
    Austria
    Thanks, diversenok & David. :thumb:

    Just to be sure: You mean updating to Sandboxie Plus or to Sandboxie Classic (in their recent versions)?
     
  7. Buster_BSA

    Buster_BSA Registered Member

    Joined:
    Nov 29, 2009
    Posts:
    735
    Thanks diversenok and David for the security fixes!
     
  8. deugniet

    deugniet Registered Member

    Joined:
    Nov 25, 2013
    Posts:
    972
    +1.
     
  9. diversenok

    diversenok Registered Member

    Joined:
    Oct 7, 2018
    Posts:
    18
    Location:
    Russia / Netherlands
    I meant David's fork. As David mentioned above, which UI you use does not change anything regarding security or compatibility.
     
  10. Buster_BSA

    Buster_BSA Registered Member

    Joined:
    Nov 29, 2009
    Posts:
    735
    For me "Sandboxie Plus" is David's fork, independently of the GUI you use.
     
  11. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,918
    Location:
    .
    0.5.4
    Code:
    |Time|         |Message|                                                                                                                   
    
    16:21:13.743   Sbie Directory: C:\Program Files\Sandboxie-Plus                                                                             
    16:21:13.743   Loaded Config: C:\WINDOWS\Sandboxie.ini                                                                                     
    16:22:19.376   SandboxieDcomLaunch.exe (8692): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000253                     
    16:22:19.439   msedge.exe (2464): SBIE1231 Initialization failed for process msedge.exe [C0000080 / 22]                                     
    16:22:19.440   SandboxieRpcSs.exe (9300): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037                         
    16:22:19.441   SandboxieRpcSs.exe (9300): SBIE2203 Failed to communicate with Sandboxie Service:  connect C0000034                         
    16:22:19.471   msedge.exe (8052): SBIE1231 Initialization failed for process msedge.exe [C0000080 / 22]                                     
    16:22:24.274   msedge.exe (7624): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037                                 
    16:22:24.275   msedge.exe (7624): SBIE2203 Failed to communicate with Sandboxie Service:  *GUIPROXY_00000001; MsgId: 14 - msedge.exe [C0000080]
    16:22:24.426   msedge.exe (7624): SBIE2203 Failed to communicate with Sandboxie Service:  connect C0000034                                 
    16:22:24.429   msedge.exe (7624): SBIE2203 Failed to communicate with Sandboxie Service:  *GUIPROXY_00000001; MsgId: 14 - msedge.exe [C0000080]
    16:22:25.691   msedge.exe (7624): SBIE2203 Failed to communicate with Sandboxie Service:  *GUIPROXY_00000001; MsgId: 14 - msedge.exe [C0000080]
    16:22:28.772   msedge.exe (7624): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037                                 
    16:22:30.037   msedge.exe (4700): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037                                        
    Code:
    |Time|         |Message|                                                                                                                    
    
    16:31:08.639   Sbie Directory: C:\Program Files\Sandboxie-Plus                                                                              
    16:31:08.639   Loaded Config: C:\WINDOWS\Sandboxie.ini                                                                                      
    16:33:28.861   SandboxieDcomLaunch.exe (9076): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000253                      
    16:33:28.894   msedge.exe (10120): SBIE1231 Initialization failed for process msedge.exe [C0000080 / 22]                                    
    16:33:28.904   SandboxieRpcSs.exe (2280): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037                          
    16:33:28.907   SandboxieRpcSs.exe (2280): SBIE2203 Failed to communicate with Sandboxie Service:  connect C0000034                          
    16:33:28.939   msedge.exe (3772): SBIE1231 Initialization failed for process msedge.exe [C0000080 / 22]                                      
    16:33:36.912   msedge.exe (9288): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037                                  
    16:33:36.913   msedge.exe (9288): SBIE2203 Failed to communicate with Sandboxie Service:  *GUIPROXY_00000001; MsgId: 14 - msedge.exe [C0000080]
    16:33:37.014   msedge.exe (9288): SBIE2203 Failed to communicate with Sandboxie Service:  connect C0000034                                  
    16:33:37.016   msedge.exe (9288): SBIE2203 Failed to communicate with Sandboxie Service:  *GUIPROXY_00000001; MsgId: 14 - msedge.exe [C0000080]
    16:33:38.125   msedge.exe (9288): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037                                  
    16:33:38.834   msedge.exe (9288): SBIE2203 Failed to communicate with Sandboxie Service:  *GUIPROXY_00000001; MsgId: 14 - msedge.exe [C0000080]
    16:33:39.442   msedge.exe (10164): SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037                                       
    Code:
    SBIE2203 Failed to communicate with Sandboxie Service:  *GUIPROXY_00000001; MsgId: 15 - msedge.exe [C0000034]
    SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037
    SBIE2203 Failed to communicate with Sandboxie Service:  request C0000037
    SBIE2203 Failed to communicate with Sandboxie Service:  *GUIPROXY_00000001; MsgId: 14 - SandboxieRpcSs.exe [C0000080]
    
     
    Last edited: Jan 7, 2021
  12. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    3,921
    Location:
    Mexico
    When launching Chrome on W10 sbie msgs say:
    Code:
    
    |Time|         |Message|                                                                                                         
    
    15:36:43.863   Sbie Directory: C:\Program Files\Sandboxie-Plus                                                                   
    15:36:43.863   Loaded Config: C:\Windows\Sandboxie.ini                                                                           
    15:36:54.298   CompPkgSrv.exe (8908): SBIE1308 Program cannot start due to restrictions - CompPkgSrv.exe [Chrome_MrX]           
    15:36:55.397   chrome.exe (4564): SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1   
    15:36:56.341   chrome.exe (4564): SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1   
    15:36:57.144   chrome.exe (4564): SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1   
    15:37:24.365   CompPkgSrv.exe (6932): SBIE1308 Program cannot start due to restrictions - CompPkgSrv.exe [Chrome_MrX]           
    15:37:54.427   CompPkgSrv.exe (5108): SBIE1308 Program cannot start due to restrictions - CompPkgSrv.exe [Chrome_MrX]           
    15:37:54.938   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:54.938   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:54.938   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:54.938   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:54.938   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:54.938   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:54.938   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:54.938   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:54.938   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:54.938   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:54.938   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:54.938   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.312   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.312   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.312   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.313   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.313   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.313   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.313   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.313   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.314   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.314   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.314   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.314   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.583   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.584   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.584   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.584   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.584   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.584   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.585   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.585   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.585   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.585   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:55.585   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:55.585   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:56.085   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:56.085   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:56.693   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:56.694   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:56.694   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:56.694   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:56.694   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:56.694   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:56.695   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:56.695   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:56.695   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:56.695   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    15:37:56.695   PID 4032: SBIE2214 Request to start service 'bits' was denied due to dropped rights                               
    15:37:56.695   PID 4032: SBIE2219 Request was issued by program SandboxieDcomLaunch.exe [Chrome_MrX]                             
    
    
     
    Last edited: Jan 7, 2021
  13. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    1,006
    Location:
    Viena
    SBIE2214
    do you have ProtectRpcSs=y enabled? I just realized that when its on and the new system token protection is not off, in one place you end up without the required rights to start services
    I'll remove ProtectRpcSs from the next build entierly to avoid those issues

    SBIE1308
    apparently you have start restrictions on and that's the result

    SBIE2101
    does this happen also when you remove/disable ProtectRpcSs=y ?


    SBIE2203
    message id 14 hmm... GUI_ENUM_WINDOWS
    message id 15 hmm... GUI_FIND_WINDOW
    strange why would that failed I haven't changed anything on that particular part.


    Also on my system with a default configured box chrome 86 starts just fine...
    please remove the ProtectRpcSs=y entries from your ini and see if that resolves the issue.
     
  14. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    3,921
    Location:
    Mexico
    Yes I have some so please ignore them I just rapidly copy-paste the msgs
    No I don't. I haven't seen or enabled such setting before
     
  15. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,918
    Location:
    .
    Where may I find "ProtectRpcSs=y" entries from your ini
     
  16. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    3,921
    Location:
    Mexico
    Anywhere, individual sandboxes or global settings as a template.
     
  17. Special

    Special Registered Member

    Joined:
    Mar 23, 2016
    Posts:
    454
    Location:
    .
    Getting tons of errors for various programs I use too, please test this FFS (what happened to beta/pre-release builds?), mass reporting of errors like above should not be happening hours after a release, especially with popular programs like Edge and Chrome, clearly shows things are just being changed and shot right out the door.
     
  18. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,918
    Location:
    .
    Okay....I'm not finding "ProtectRpcSs=y" with Edit ini [GlobalSettings] [UserSettings_*] [Edge] [Default] etc..

    Edit: found "ProtectRpcSs=y" with (not used) [Hardened] box
    png_8707.png
     
    Last edited: Jan 8, 2021
  19. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,918
    Location:
    .
    FWIW ~ I'm back with 0.5.3b / 5.45.2 running with the Sandboxie.ini & Templates.ini (isaak654) before my 0.5.4 / 5.46.0 clean install -
     
    Last edited: Jan 7, 2021
  20. Peter 123

    Peter 123 Registered Member

    Joined:
    Feb 1, 2009
    Posts:
    395
    Location:
    Austria
    Various issues with Google Chrome (which I assume that have to do with Sandboxie):

    - When closing Chrome in Sandboxie (I have it in its own sandbox) I cannot open it any longer outside of Sandboxie.

    - I also cannot open it a second time within Sandboxie. Only after restarting my computer it works again (for one time).

    - The tray icon of Sandboxie suddenly is gone.

    Happened with Google Chrome Portable (v 87.0.4280.88 ) and Sandboxie (v. 5.46.0).
     
    Last edited: Jan 7, 2021
  21. Peter 123

    Peter 123 Registered Member

    Joined:
    Feb 1, 2009
    Posts:
    395
    Location:
    Austria
    Addition:

    Obviously the problems between Chrome and Sandboxie affect the behaviour of Sandboxie in general:

    As mentioned above, Chrome has its own Sandbox on my computer. In another sandbox I have my standard browser (= Firefox, v. 84.0.1). After having started Chrome within Sandboxie (and even after having it closed again) I cannot start any longer Firefox in its sandbox. I get the following messages:

    First
    and then
    After restarting the computer fortunately all seems to work fine again. (As long as I do not get in touch with Chrome in Sandboxie. :D)
     
  22. guest76

    guest76 Registered Member

    Joined:
    Jan 7, 2021
    Posts:
    1
    Location:
    America
    https://i.ibb.co/f2pwd5q/error2.png

    Hello I'm using 5.46.0 classic 64 bit for 7 with provisional driver.

    How do I turn off "Messages from Sandboxie"? I keep getting this error, but it works fine. Windows explorer opens and works. I just want to ignore the error.
     
  23. davi

    davi Registered Member

    Joined:
    Jul 3, 2020
    Posts:
    19
    Location:
    RO
    Tested the new 0.5.4 release and added also the recommended options to GlobalSettings to harden sandboxie ClosePrintSpooler=y, OpenSmartCard=n and OpenPrintSpooler=n.
    After a round of test this are my results:
    Edge works fine for me (except for some warnings like msedge.exe (3084): SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1 ).
    Excel 2019 with office clicktorun also works sandboxed (never had problems with excel/word but i've seen people in the comments who encountered problems). Firefox works great.

    What is not fine is that a shortcut I have on the real desktop that points to a program installed in a sandbox, when started it would start unsandboxed, ex:
    "E:\Sandbox\Me\GB202011\drive\E\FMRTE 20\FMRTE.exe"
    I had a link created to the location above. When accessed it would always start sandboxed (the app is installed directly in that sandbox) but now after requesting admin rights (the app requires admin rights to be used so it can read other process memory) it started unsadboxed. And the app is not even installed in the real system, i had to explicitly open an sandboxed explorer instance and go to E:\FMRTE 20\FMRTE.exe and then the app ran sandboxed.
    I have other programs/games that are started in the same way, link created to their path in the sandbox, but only this app always starts unsanboxed.
    So to test this even further, I've installed it again in a fresh DefaultBox and the behavior is the same, after installation is done and if i go in an unsandboxed explorer and run "d:\Sandbox\Me\DefaultBox\drive\E\FMRTE 20\FMRTE.exe" it will start unsandboxed.
     
  24. davi

    davi Registered Member

    Joined:
    Jul 3, 2020
    Posts:
    19
    Location:
    RO
    I also tested with the forced folders feature, i've added ForceFolder=d:\Sandbox\Me\DefaultBox\drive\E\FMRTE 20 to [DefaultBox] and now when the program is ran from a link with the path "d:\Sandbox\Me\DefaultBox\drive\E\FMRTE 20\FMRTE.exe" it starts sandboxed. But this behaviour is not expected, because every program installed in the sandox should open in that sandbox without using the ForcedFolder/Program feature.

    Also while testing I've seen a bug in the new UI, when trying to modify/add Forced Programs it would not apply/save them so I went and added the ForceFolder setting manualy inside the ini. Actually i can't modify any specific sandbox option in the new UI, not even in the old UI. At least the old one gives an error: Failed to record configuration setting ForceProcess in section DefaultBox: C0000023) and also frequent errors like Failed to record configuration setting SbieCtr_nextUpdateCheck in section...
     
    Last edited: Jan 7, 2021
  25. Peter 123

    Peter 123 Registered Member

    Joined:
    Feb 1, 2009
    Posts:
    395
    Location:
    Austria
    After restoring an image I tried to download Sandboxie again from the above link. But now in Firefox from the offered four versions the download of three of them would work fine and exactly for the one that I would need the download crashes (Classic-x64-v.5.46.0).

    PS:
    Obviously it has to do with the fact that the file is regarded as dangerous:
    I made an attempt to download with Chrome and there came a warning that I try to download a suspicious file. After clicking the (hidden) option to keep it, the download finally succeeded. - That's all so tiring. :thumbd:
     
    Last edited: Jan 7, 2021
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.