user10072023github
commented
11 months ago Glad to hear a replacement is on the horizon. I like that you're focused on core features for the time being as there's nothing I dislike more than bugs. How much will you be able to replicate the registry tweaks functionality from Priv10? I'm most fond of the idea of getting that worked out asap. I baselined on v2004 back in 2020 when I finally made the switch over to Win10...could I ask to please still keep that version on the list to test against? Thanks
DavidXanatos
As you may have noticed, PrivateWin10 has not seen much development in the past 2 years. The reasons were many, not only lack of time due to Sandboxie-Plus, but also a couple conceptual issues with the design which can not be fixed without using a driver, as well as the substantially higher amount of fiddling around required to create a advanced UI using XAML in comparison with just Qt widgets.
So, moving forward I’m implementing a successor which will be called MajorPrivacy, a much-needed rebranding given that a private Windows 10 is not enough now we also need a private Windows 11 and soon 12 and so on and so forth…
MajorPrivacy will be like most of my other projects written in C++ and be using Qt Widgets for the user interface, and bring a new driver to add the much-needed kernel features to properly enforce advanced privacy presets.
In addition to the functionality PrivateWin10 offered, the Major will implement own rule-based software restrictions, i.e. the ability to prevent unauthorized or undesired applications from running. It will also bring a folder protection feature allowing to restrict access to confidential data to authorized processes. Its kernel-based process isolation abilities will ensure that the authorized processes cannot be tempered with providing the highest level of protection from other processes, and even a high level of protection from adversarial processes running with administrative or system privileges.
In the initial release a couple minor Priv10 features will not be included, like the filtering DNS proxy, these will be added later. Furthermore, additional new features will be added, a per process DNS filter using a hook dll, proxy injection also the driver will later implement an own firewall engine allowing for more control then is possible by only leveraging the windows firewall rules. The driver’s ability to control and block register accesses will allow to prevent unauthorized alteration of firewall rules and other guarded registry presets.
The UI concept for the Folder Control and Execution Restriction tabs will be analogues to Network Firewall tab in Priv10, a list on the left containing Program Items which can be a single program, service or a group of those, a rule list on the top right and status/logs on the bottom right. The UI will look not as modern as priv10 but will resemble SandMan.exe style wise.
Let me know what other features you would want to see or which priv10 aspects you would like to have changed.
The plan is to have a first release sometime end of this year.