I've described about one time installers early.What is the gain from saving outgoing packets somewhere rather than blocking connection until decision is taken?
@rashmi described about HiBit Uninstaller.
I've described about one time installers early.What is the gain from saving outgoing packets somewhere rather than blocking connection until decision is taken?
You mean when saving outbound packets somewhere, just selecting allow connection will lead to resuming internet connection of HiBit uninstaller without restarting the uninstaller?I've described about one time installers early.
@rashmi described about HiBit Uninstaller.
There is a small bit of convenience when you try to install a program such as a browser (which generally needs to pull resources online to actually install). If you block the connection, it will fail and tell you to connect, and so you have to double click the .exe again to start again after allowing. If the connection is saved somewhere else, you don't need to double click the .exe again. I'm not sure how reliable it would be for every program though.What is the gain from saving outgoing packets somewhere rather than blocking connection until decision is taken?
Where are those packets saved? SSD? and what is the fate of saved packets if I choose block connection? are they deleted automatically or I have to delete them manually?In a nutshell, saving those outgoing packets turns an immediate, harsh stop into a brief pause. It keeps your apps happy and responsive, prevents headaches, and gives you a bit more control over your internet traffic.
Those waiting packets are temporarily held in your computer's RAM, not your SSD. If you choose to block the connection, those saved packets are automatically deleted and the application trying to send them gets the message that it's a no-go.Where are those packets saved? SSD? and what is the fate of saved packets if I choose block connection? are they deleted automatically or I have to delete them manually?
Looks for me too much hassle to save me clicking retry after selecting allow connection!Those waiting packets are temporarily held in your computer's RAM, not your SSD. If you choose to block the connection, those saved packets are automatically deleted and the application trying to send them gets the message that it's a no-go.
Fair enough! But think of it this way, the firewall's just giving you a second chance to catch a runaway packet before it causes trouble. Better a little hassle than a lot of oops!Looks for me too much hassle to save me clicking retry after selecting allow connection!
Yes, exactly.You mean when saving outbound packets somewhere, just selecting allow connection will lead to resuming internet connection of HiBit uninstaller without restarting the uninstaller?
All of them; it is the first time for me to know this mechanism.Yes, exactly.
I think, all old school firewalls worked like this (e.g. Agnitum Outpost Firewall).
Comodo Fw, NetLimiter, Portmaster work like this too.
The advanced rules still need some work. Minimal Firewall is a true frontend, so I suggest just using Windows Firewall or in cmd as admin, type in something like this:I have tried out Minimal firewall but I am not sure how it is supposed to work.
I have a long list of service rules that I am unable to delete.
I am unsure how to add an UWP App. If I allow a UWP App in Pending connections I do not get an UWP App rule.
I am trying to create an advanced rule to allow a program to access anything on the local network only. I have tried 192.168.0.1-192.168.0.255 and LocalSubnet for the IP but Minimal Firewall just crashes.
netsh advfirewall firewall add rule name="Whatever you want to name it" dir=out action=allow program="C:\Path\Program.exe" remoteip=192.168.0.0/24 enable=yes profile=private Wildcards are just for convenience. It just makes it so it auto-blocks or auto-allows when Minimal Firewall is turned on, by adding a rule to Windows Firewall.Thanks.
I think I understand the services now. It is a list of all services and not a list of rules.
I assume the wildcards will only work when the program is running. Do you plan to make it work without a UAC prompt? I am looking for a firewall that is easy to use and does wildcards.
hi @deminimis, do your firewall hold DDOSS attacks at kernel level (sys -> dll-> exe) for windows ?
if yes could you tell us how exactly ?
any EV certificate signed on your app ?
those question is because there is no garanty inside your GPL liscence,
have a nice day ^^
I debugged quite a few errors and fixed some memory management, and so this update should provide a much more stable experience. Please see below for information on creating new rules.
Bug fixes
- Modified three methods in FirewallActionsService.cs to ensure that when a simple rule is created, it's not restricted to your current network type. This change I made a couple updates back has led to continuous problems with popups even if there was a rule. It should be fixed now. However, you will probably need to delete the rules that say something other than "any"
- Fixed confusion between reading service/application, causing the program to alert you of a blocked connection even if you already had a rule.
- Important: This fix only applies to new rules you create. For the apps that are still causing problems, you should delete their existing rules from the "Rules" tab and then recreate them. The new rules will be saved with the correct, broader scope and will work correctly on your VPN.
- To do this, simply go to the rule tab, click the protocol column to sort by protocol, and shift+select all the rules that say something other than "any" in the protocol.
- Fixed audit counter.
- Should now start at startup on Windows 10 if you have that setting added.
- Updated backend monitoring/memory issues.
Other
- Consolidated code.