Man , you have a great software, verry usefull thanks, i could pay for it for sure in a future time ^^
Fort Firewall
- Thread starter tnodir
- Start date
@tnodir Can you please explain to me how zones work in fort firewall? There are three option but when I use use 3rd pic tick mark one it just disables the internet for that application but works in the greyed out option.
@JustInTime App's zones can have 3 states:
- default disabled - the zone is not used
- included - app can connect only to these set zones
- excluded - app can not connect to these unset zones
- default disabled - the zone is not used
- included - app can connect only to these set zones
- excluded - app can not connect to these unset zones
So tick mark means app can only connect to these zones and grey box means app can't connect to these zones. Is it correct?
@JustInTime Yes, correct.
OTOH, you can block the WindowsSpyBlocker addresses for all apps by selecting it in the Options: IP Addresses: Internet: Block addresses.
OTOH, you can block the WindowsSpyBlocker addresses for all apps by selecting it in the Options: IP Addresses: Internet: Block addresses.
Last edited:
There are several requests for UI from users in the Issues/Discussions. We may implement them in the future.
I was thinking of creating windows update app group which I can enable only when I want to update. Can anyone tell me what services to allow for windows update?
I enable the following services for Windows Update: "BITS", "DOSvc", "WUAUServ".
But in general, you can determine which services are needed by the Statistics: Connections window:
- find services by Process ID of svchost.exe
Yes, they will be blocked by default.
See the Options: "Block traffic for disabled App Groups" flag.
Fort Firewall 3.19.4
- UI: MyFort: Add "Portable Installed" label (#634).
- UI: Rule: Add "Log Allowed/Blocked Connections", "Terminate: Alert" flags (#241).
- UI: Connections: Show alerted action icon (#241).
- Driver: Add "option(log, nolog, alert)" filter function (#241).
- Installer: Skip password checking on auto-update (#629).
Hi 
First of all, thank you for your amazing work on Fort Firewall — I honestly think it’s already better than popular alternatives like GlassWire.
I’d like to let you know that if the next major stable version of Fort Firewall (v4, or even v5 if you need more time) passes WHQL (Windows Hardware Quality Labs) certification and is marked as HVCI-compatible (Hypervisor-protected Code Integrity), I would be very happy to support the project — either by purchasing a license or making a donation via PayPal.
I believe many other users would also greatly appreciate having Fort fully compatible with modern Windows security features without the need to disable Core Isolation.
For me, a lifetime license per major version sounds fair. Perhaps you could also discuss with Microsoft the possibility that minor updates under the same major version remain valid for HVCI certification.
And if you encounter difficulties with Microsoft regarding minor updates, I would gladly help by sending them some advertisements or raising awareness — at no cost to you.
Once again, thanks for building such a solid alternative firewall.
Best regards,
ps : don't be fear too much about Microsoft “stealing” your project.
Since Fort Firewall is open source (GPLv3), everything is public and timestamped. If Microsoft ever tried to copy your work, it would be very obvious to the community and damage their reputation. Also, your driver is technically different and independent from the Windows Firewall stack. If Microsoft ever wanted to integrate something similar, they would still need to rely on the signature of your driver (or build a new one from scratch) in order to give it the proper rights inside Windows. This is a strong protection of your originality, and even though GitHub is 100% owned by Microsoft today, the timestamps and the hashes of your code do not belong to them. These are cryptographic proofs, independent of ownership, which guarantee that your work can always be verified and attributed to you. This means that Microsoft cannot simply take your project and pretend it’s theirs — the history of your commits and the hashes will always protect your authorship.
First of all, thank you for your amazing work on Fort Firewall — I honestly think it’s already better than popular alternatives like GlassWire.
I’d like to let you know that if the next major stable version of Fort Firewall (v4, or even v5 if you need more time) passes WHQL (Windows Hardware Quality Labs) certification and is marked as HVCI-compatible (Hypervisor-protected Code Integrity), I would be very happy to support the project — either by purchasing a license or making a donation via PayPal.
I believe many other users would also greatly appreciate having Fort fully compatible with modern Windows security features without the need to disable Core Isolation.
For me, a lifetime license per major version sounds fair. Perhaps you could also discuss with Microsoft the possibility that minor updates under the same major version remain valid for HVCI certification.
And if you encounter difficulties with Microsoft regarding minor updates, I would gladly help by sending them some advertisements or raising awareness — at no cost to you.
Once again, thanks for building such a solid alternative firewall.
Best regards,
ps : don't be fear too much about Microsoft “stealing” your project.
Since Fort Firewall is open source (GPLv3), everything is public and timestamped. If Microsoft ever tried to copy your work, it would be very obvious to the community and damage their reputation. Also, your driver is technically different and independent from the Windows Firewall stack. If Microsoft ever wanted to integrate something similar, they would still need to rely on the signature of your driver (or build a new one from scratch) in order to give it the proper rights inside Windows. This is a strong protection of your originality, and even though GitHub is 100% owned by Microsoft today, the timestamps and the hashes of your code do not belong to them. These are cryptographic proofs, independent of ownership, which guarantee that your work can always be verified and attributed to you. This means that Microsoft cannot simply take your project and pretend it’s theirs — the history of your commits and the hashes will always protect your authorship.
Last edited:
I've to open my own company to be able to register as MS Partner and properly sign the driver.
(I've done it in 2021 for my friend 's company and signed the driver. But it's not possible now due MS doc requirements.)
You may also like...
-
Wireshark: Your Essential Guide to Unraveling Network Traffic- Started by Divergent
- Replies: 7
-
Block Common Attacks: A Beginner's Guide to Windows Firewall
- Started by Divergent
- Replies: 18
-
Orion Malware Cleaner (OMC) - By Trident- Started by Trident
- Replies: 23
-
-
Linux Firewall Basics: A Beginner's Guide to iptables for Blocking Common Attacks
- Started by Divergent
- Replies: 1