I see several people on here running a VM (most of them not understanding half of what a VM is factually intended for), one or two people know some stuff about the concept of containerization, but when it comes to isolation (sandboxing), the silence here on this forum and on is deafening to say the least. Maybe it's because everyone here always wants to do almost everything the hard way, honestly I don't know. But I have come to the conclusion that nobody here is even remotely interested in this particular subject. Yet, it is not that much harder to do, nor takes that much time/effort to set up, than it is to use a Firefox addon like Multi-Account Containers─that I also use in addition to the strategy I just described.
(Both the browser settings/configuration and the sandbox settings can be different for each different instance running.) The level of flexibility that can be achieved in this manner is huge. As a matter of fact, I have set sandboxed portable Firefox as my Default Browser in Windows, and, I can run multiple instances of it at once, concurrently that is, and can do so with various many different settings in each─in parallel. I use it primarily as an added layer of browser protection with portable Firefox. I have been using Sandboxie (and now Sandboxie-Plus) for ages. It is officially hosted on GitHub, NiceAndShy If a feature sounds like it is in any way UI related it won't be available in the legacy build.įeatures that can be set using the ini manually will work in the legacy build, but you will have to configure them in the ini.Īny security or compatibility improvements are implemented in the shared components and are available in booth builds.The developer posts new versions and answers questions on the Wilders Security forum. To help you differentiate in the change log for yourself: So ideally all users should move to the Plus build as its now no longer missing any features in comparison with the classical UI. I have to be efficient with my time and every minute not wasted on cumbersome 90's technology is a minute I can spend on actually relevant core functionality. Second, and more important, its immeasurably more convenient to create and maintain Qt based UI's that those obsolete MFC based UI's from the late 90's.
I will not add any new major features to SbieCtrl.exeįeatures like Snapshots, user interactive prompts that will be expanded upon in future builds, and other will not be supported when using SbieCtrl.exeįor once the UI is really dated and not that user friendly, for example you need to save each page in the sandbox settings before you can switch to an other, etc.
As the classical UI is deprecated and provided only for legacy use there is no point in splitting the change log.
0 kommentar(er)
