Handling existing rules or new filters

henrypp / simplewall

Simple tool to configure Windows Filtering Platform (WFP) which can configure network activity on your computer.

GNU General Public License v3.0

6.08k stars 481 forks source link

Handling existing rules or new filters #162

Closed paradoxicallist closed 6 years ago

paradoxicallist commented 6 years ago

Does simplewall do anything to handle or disable already existing rules or new filters added by other programs once simplewall is activated?

ltguillaume commented 6 years ago

I'd like to know more about this, too. simplewall used to disable the default Windows Firewall rule set, but this isn't allowed anymore in newer builds of W10. I cannot find any evidence of this anymore, even though it should at least do such a thing if it's to be reliable.

In contrast, it would be awful if simplewall discarded rules introduced via these ways:

Services that try to use the Windows Filtering Platform as well, such as OpenVPN (to prevent DNS leaking) or Windscribe's firewall feature (to prevent any traffic outside the VPN connection)? These should absolutely be allowed to do their thing.
Less high-priority: new filters added by other programs to the Windows Firewall via netsh advfirewall? Will they be discarded?

ltguillaume commented 6 years ago

https://github.com/henrypp/simplewall/issues/167

henrypp commented 6 years ago

Services that try to use the Windows Filtering Platform as well, such as OpenVPN (to prevent DNS leaking) or Windscribe's firewall feature (to prevent any traffic outside the VPN connection)? These should absolutely be allowed to do their thing.

All worked with different provider (identifier/level/ etc.) and fully compatible

Less high-priority: new filters added by other programs to the Windows Firewall via netsh advfirewall? Will they be discarded?

If WF disabled - disacard.

ltguillaume commented 6 years ago

Thanks for clearing that up!

LucaPranay commented 5 years ago

Greetings and appreciations!

Any chance of me finding some pre-made custom rules file, containing the nasty telemetry apps within windows that can ideally be blocked (and what should not be blocked eventually)? - because I really don't know what is ideal and what is not to be blocked (apps such as: ntoskrnl.exe, svchost.exe, sppextcomobj.exe, smartscreen.exe, sihclient.exe, runtimebroker.exe, rundll32.exe, msiexec.exe - so far I blocked them all, and system appears to be working well)

henrypp commented 5 years ago

@LucaPranay SW already have https://github.com/crazy-max/WindowsSpyBlocker in-app