Serious Discussion Minimal Firewall

v2.7.5
  • chore: normalize line endings and file encoding by @mirbyte in #132
  • add logging to silent exception handlers by @mirbyte in #135
  • feat: show origin for auto-allowed rules by @mirbyte in #136
  • fix: narrow WFP audit check to connection subcategory by @mirbyte in #140
 
v2.8.0
This is a fairly large update
You may wish to rest your firewall when updating to this, to ensure the new audit feature works as intended. This is a security update. Basically, whenever Windows automatically creates an allow rule, it is now disabled by default. When a rule is disabled and you are in lockdown, that means the app cannot connect to the internet until you create a rule to allow it.

Bugs​

  • Added "MFW" to rules to prevent Windows from overwriting.

Backend​

  • Incremental rule fetching to reduce COM.
  • Dark theme fixes.

Features​

  • Audit tab now a history of past actions.
  • All OS rules are now disabled by default, giving you complete control. When you create a rule, it is prefixed with MFW to overwrite the Windows rule.

What's Changed​

 
v2.8.1

Bugs​

  • Removed the auto-disable OS rules, which interfere with some core networking, especially with VPN.
This version now relies on the MFW prefix on rules to avoid conflicts with OS rules. It retains the logging in the Audit tab (see v2.8.0 notes).

If you downloaded version 2.8.0, please go to the settings tab and click "Revert Windows Firewall." That version disabled all Windows rules by default (thus blocking those app/service acces to the internet).

You do not need to revert anything if you did not download v2.8.0, but you may want to just to add the MFW prefix to rules to ensure Windows does not create its own rules on top of those without telling you.
 
v2.8.2

Bugs​

  • Turning off popups in settings now closes all pending popups (but keeps them in dashboard).

Backend​

  • Refactored theming
  • Tab performance upgrade

UI​

  • Updated fonts
  • Removed some custom ui
This is a fairly large UI code refactor. It should slightly increase performance. If you notice any quirks, please open an issue.
 
v2.8.3
  • fix: sidebar tab icon and text alignment by @mirbyte in #157
  • Fixed UWP filter in Rules tab.
  • More support for foreign languages (removing language localization).
 
It's getting better, but I still have some issues from time to time.
Let me know if there are any issues you want fixed if you aren't adding on Github issues, and I'll try to sort it out.

I just added domain blocking in v2.8.4. When I have more time I have a larger update planned related to that and live connections, which I have been working on in my unreleased rust firewall app.
 
Let me know if there are any issues you want fixed if you aren't adding on Github issues, and I'll try to sort it out.

I just added domain blocking in v2.8.4. When I have more time I have a larger update planned related to that and live connections, which I have been working on in my unreleased rust firewall app.
Thanks for the update. I have tested v2.8.4 and the new domain blocking is working smoothly for me so far. No immediate issues to report.

The planned update for live connections in the Rust app sounds promising, looking forward to seeing how that evolves. Keep up the great work.
 
I did not try since its earliest versions; felt clunky; either using Avast firewall with the rest of the suite or Fort firewall or Simplewall with MD.
Fort Firewall is a no go for me. I would never disable a core security feature for it. That was the reason I stopped using Kaspersky. Regarding Simplewall, I did not like it and it felt complicated. Moreover, it does not edit WF rules, but rather creates low-level wfp rules.
 
  • Like
Reactions: simmerskool
That was the reason I stopped using Kaspersky
I was using Kaspersky free; did not have to disable core isolation!
Moreover, it does not edit WF rules, but rather creates low-level wfp rules
The same applies to Fort firewall; both do not disable Windows firewall; they run alongside.
Only Avast firewall disables Windows firewall.
 
I was using Kaspersky free; did not have to disable core isolation!

The same applies to Fort firewall; both do not disable Windows firewall; they run alongside.
Only Avast firewall disables Windows firewall.
I was talking about Kaspersky virtualisation. To use it you need to disable core virtualisation in windows.

Regarding, Simplewall, it is different than any other Windows firewall guis. Instead on creating firewall rules in Windows firewall, it does create low-level wfp rules. This why uninstalling it, does not remove the rules. At least that's my understanding of how it works.
 
Even in paid K. home product You don't have to disable W. Core Isolation, yes You will lose K. hardware virtualization, but it is only used in Safe Money session. Even KES (business product) I use in my main, does not have K. hardware virtualization, and I keep W11 Core Isolation enabled without any issue.
 
Regarding, Simplewall, it is different than any other Windows firewall guis. Instead on creating firewall rules in Windows firewall, it does create low-level wfp rules. This why uninstalling it, does not remove the rules. At least that's my understanding of how it works.
Indeed, it isn't a WF frontend but uses Windows Filtering Platform and is a separate firewall with deep hooks in the system.
 
Even in paid K. home product You don't have to disable W. Core Isolation, yes You will lose K. hardware virtualization, but it is only used in Safe Money session. Even KES (business product) I use in my main, does not have K. hardware virtualization, and I keep W11 Core Isolation enabled without any issue.
Thank for point this out. I thought it is needed for other components.
 
  • Like
Reactions: harlan4096
To use it you need to disable core virtualisation in windows
I uncheck this option in both Kaspersky free and Avast free as it is not enabled in my BIOS.
This why uninstalling it, does not remove the rules
All rules created by Simplewall get removed after its uninstallation; to be on the safe side, just click disable protection icon before uninstallation.