I've decided to quickly add a fun feature to block programs starting. Please test it in v3.9.0-test01. What do you think about this feature?
Fort Firewall v3.9.0 UI: Programs: Add "Kill Process" option. UI: Fix "Collect Blocked Connections" functioning when "Collect Traffic Statistics" is turned off.
Fort Firewall v3.9.1 UI: Add "My Fort" window. UI: Options: Tray: Add "Show Icon" flag. UI: Options: Hot Keys: Add "Global" flag. UI: Show Traffic Graph when "Collect Traffic Statistics" is turned off.
Fort Firewall v3.9.2 UI: Activate already running instance, don't show a warning. UI: My Fort: Show menu on activation. UI: Update main icon. UI: Add ability to use custom icons/ folder from current working dir. UI: Programs: Rename "Purge All" to "Purge Obsolete".
Fort Firewall v3.9.3 UI: "My Fort": Some controls moved from "Options". UI: Reorganization of "Options" window. UI: Added "Menu" button to all windows. UI: "Options": Added "Purge Obsolete on startup" flag. UI: Don't ask for a password if an open window exists. UI: Updated SQLite to v3.42.0
Fort Firewall v3.9.4 UI: Options: Traffic Graph: "Reset to defaults" button added. Driver: Existing connections are not closed during installation. Installer: Check whether Windows version is 10 2004 or newer.
I installed Fort firewall 3.94 under windows 11. I have several problems. I have several questions.. 1. Ask to connect filter mode is always disabled, I could not find a way to enable it...is it not implemented yet or is there a way to enable this feature? 2. Does Auto Learn mode allow only signed software? 3. there is IP based and applıcation based filter methods but they seem to exclusive, what If I want to disable a specific app to reach a specific IP only? 4. Is there a way to see a list of allowed connections ? there is a log of blocked connections under statistics blocked connections tab, but there is no allowed connections tab? In general no big issues, great job and good software with a really high probabilty of becoming a great firewall!!!!
@xegean Thanks for feedback. Same answer to all your questions: not implemented yet. It allows all software. There is an issue to handle programs' signatures in GitHub. Do you have a specific use case for this feature? I think, malwares are signed anyway.
Fort Firewall v3.9.5 UI: Options: Add tag to language list. UI: Options: Confirm Quit by default. UI: Options: Tray: Animate alert by default. UI: Programs: Refresh on app group's enabled flag change. UI: Close windows by Escape key immediately. Driver: Remove processes enumeration on startup.
Fort Firewall v3.9.6 UI: Traffic Graph: Fix crash after sleep. UI: Options: Apply "Tray: Show Icon" changes immediately. UI: Options: Add "My Fort: Auto-Show Menu" flag. UI: Tray Menu: Fix Traffic Graph's checked state. UI: Update main icon.
Fort Firewall v3.9.7 UI: Monitor services for driver. Installer: Start program automatically after installation.
Fort Firewall v3.9.8 UI: Programs: Accept File Drops. UI: Auto-install driver in portable mode. UI: Add "-i boot_filter" argument. UI: "no-cache" can't be used with service. UI: Run scripts in minimized window.
Fort Firewall v3.9.10 UI: Programs: Add ability to search by path and name. UI: Options: Add "Alert Message" flag to show system message notification about new program(s). UI: Options: Add "Use System Regional Settings" flag. UI: Rename "Stop ..." to "Block ...".
Fort Firewall v3.9.11 UI: Drop excessive blocked log packets on slow machines. UI: Optimize icons by FileOptimizer. UI: Update SQLite to 3.43.0
I have Win 8.1 now, and I am looking at Win 10 firewalls before I buy a new PC with Win 10. @tnodir - Thank you for your reply to my question in https://www.wilderssecurity.com/thr...block-win10-phoning-home.452327/#post-3161305 Have you (or any user) tested Fort Firewall's boot-time filter to see if it blocks internet access by the MS OS? Specifically, if you set the Fort Firewall filter mode to "Block, if not allowed" and allow only DHCP under Services, do you see any internet/WAN accesses in your router or hardware firewall logs? DHCP sends to address 255.255.255.255 using UDP port 67, which is on the LAN, not the WAN. https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol
Use following flags in the Options: Self Protection: - "Block traffic when FFw is not running" - "Filter Local Addresses" And review the Options: Internet Addresses: "Exclude" list. I.e. remove/comment the "255.255.255.255/32" from it, so this address is not auto-allowed. Boot-time filter was tested in this issue.
