7G Firewall: September 2020 Update
Pleased to announce that the 7G Firewall is updated to version 1.3 (September 3rd, 2020). Now available for download, 100% free and open-source as always.
7G Firewall: summary of changes
Changes to 7G Firewall include:
- Reorders some rules within the firewall
ENDfor logging rules
- Renames log files and updates logging rules
- Removes logging loop-protection rules
- Adds some new patterns to the firewall
- Removes some patterns from the firewall
This update was big focus on better performance and even lower rate of false positives. Plus the logging script was improved and better integrated with the firewall. Oh yeah, also fixed several bugs in this update.
Check out complete 7G Changelog »
7G Logging Script
Bonus! Also updated the 7G Logging Script to version 1.2. Changes were minor, including renaming the logging files and fixing a bug with an older version of PHP. Like the 7G Firewall, the logging script is 100% FREE and open-source for everyone. So check it out and download the latest version.
I want to give a huge Thank You to everyone who provides feedback and bug reports for 7G and the logging script. This latest update is dedicated to you, thanks for helping to make the 7G firewall the best it can be.
Learn more and download the latest:
thanks Jeff – your work is much appreciated
hope you’re doing exceedingly well
Thanks Jeff! Question: Would you run a security plugin (e.g., iThemes Security) in addition to 7G?
Personally I do not. But adding more layers of security always is a good idea.
Thx for that :)
Would it be more efficient on a WordPress site to use the 7G firewall directly in the .htaccess or the BBQ plugin (who use 5/6G if I’m correct) ?
Hi Julia, 7G/.htaccess is recommended because of the performance benefits. Plus 7G is stronger than BBQ in many respects.
Thx for your insight
Waiting for 8g htaccess beta tester <3
One question not directly related to this update but to the 7G firewall in general.
I’ve been using it since version 5G much to my delight, but I’m about to move from Apache to Nginx and therefore, I won’t be able to use it anymore. Could I ask what you would recommend ?
– Try to convert all those rules for Nginx.
– Use your BBQ: Block Bad Queries WordPress plugin instead.
I could of course also just use Nginx as a reverse proxy and keep Apache behind, but I find this solution a bit too cumbersome.
Thanks in advance for your views on the subject.
Go with BBQ, unless you can find a copy of the 7G Nginx version. I’ve heard it’s been adapted for Nginx (and is in use at certain web hosts), but not sure if posted anywhere online.
Hello! Is there a way to deploy the scripts on nginx stack? My hoster doesnot provides Apache hence no .htaccess
I’ve heard of 7G converted to Nginx, but have not been able to get an actual copy. You might try searching around, maybe it is posted somewhere online.
I want to say thankyou for your work on 7G Firewall. It now runs on my server and I am fully satisfied. I have placed further filters in .htaccess for my special needs.e.g. I modified your logging php script. It now writes into several additional logfiles for specific purposes,for instance for reports I send to AbuseIPDB. I added further php scripts (which are called in the header of each webside) which check proxies and blacklisted hosts.
Thank you, Bernd! Sounds like you got it dialed in :)
Any good thing, for a safer “Web-Community”!
Some of the REGEX rules, I have also added to my PHP Firewall filters too. Seems the worst of the worst out there, are getting pretty persistent (mostly “bots”, of course). – So, these filters are becoming more a necessity.
Not sure if you have had much chance to play around with mod_rewrite’s “RewriteMap”-directive much, but it has become very effective in enforcing IP block-outs. – There again, the usual managed web-hosting plans usually do not have access to it available to the customer, because it must be set up within “Virtual Host” conf’s.
Back in the saddle (for a time). Keep up the great work! – Also have a “feed” channel from your blog (here) set up on my own site (I noticed something like a “crawl” or “refer” from your domain in my logs). – So that may account for a few extra “hits” in your logs, originating from my domain? ? ?
Does the 7G 1.3 update come with the same code placement as mentioned in the 6G Notes? My WordPress is installed in its own directory.
I can’t seem to find this info in any of the pages related to 7G.
Greetings from Transylvania!
Yes, the same install steps apply to all versions of nG Firewall.