FireWall Script RC1 Released

RC 1 of FireWall Script has been released to the downloads area.

RC1 fixes a few reported issues since the release of Beta 4. Specifically

• Bad date listed on home page when there are no attacks logged
• Error messages not highlighted properly
• Extremely large block logs cause resource issues

With RC1, blocked request logs will be backed up daily, just like visit logs. This should help keep the blocked request logs at a manageable size, reducing memory overhead.

We expect one more RC release (depending on bugs reported following this release of RC1), hopefully followed by the final release. After final release, we will evaluate where to go next. We are considering, for example, a MySQL version of the software (where logged requests are stored in mysql instead of flat file - this would make the software much more efficient, but does require you to have MySQL available).

As always, thank you for your patience and support while we work to make our product the best around!

Beta 4 Released

Beta 4 of FireWall Script has been released to the downloads area.

Beta 4 fixes all issues reported to our bug tracker, and has code added to combat the scattered reports of an error referencing "__autoload". Anyone still experiencing an error about "__autoload" after this release should submit a ticket so we can nail this one down for the next beta/RC release.

Additionally, in Beta 4, when viewing the full log of a blocked request, the part of the request that triggered a rule will be highlighted when possible. For instance, if you have a rule to block "union" in the query string, and "union" was found causing the request to be blocked, it will be highlighted in the logs to help you more easily identify what is getting blocked.

Please comment on this release - we hope we're nearing an RC stage at this point, which should go rather quickly with the time spent on the beta releases.

As always, thank you for your patience and support while we work to make our product the best around!

BETA 3 Released + Other Updates

Ok all - we've been working our fingers off trying to get you guys all set and have some updates to report.

Firstly, BETA 3 is now available. Updates in this release include:

• Bug fix: foreach warning in skin_logs
• Bug fix: no rules causes problems
• Bug fix: long urls in logs stretch page
• Bug fix: escaping of bad data in logs
• Ability to disable traffic logging for busy sites
• Support for subdomains in licensing scheme

As noted, we've added support for subdomains in this release.

Dan announced the other day that our affiliate program has been kicked off. Now you can earn money by referring people to FireWall Script!

We've also got our additional domain licensing system in place. If you have already, or wish to, purchase additional domains from your client area you can do so. Afterwards you'll just enter the site url into the addon purchase record. We manually approve all additional domain purchases to prevent abuse, but once approved your key will be displayed in your client area.

There's a ton of other backend things going on that we've got cleared up as well.

Please check out BETA 3 and report any issues to our bug tracker. Feature requests can be reported to our feature requests category. While they may not make it into 1.0.0, we're always interested in what our customers would like to see in future versions, as you help shape the future of the software.


One last reminder - you are required to add a copyright to your home page when using FWS. We've got our copyright checking system online and have noticed that many of you don't have a copyright on your website homepage at this time. We're going to give people some time to get them in place of course, but the copyright is required, and we'd hate to have to disable a license for something so easy to rectify.

If you have any questions ask away, otherwise test out the new version and let us know how it works for you.

More Information about FWS

What is FireWall Script?

FWS is a PHP-based firewall for your website. By including it in your script, and configuring the rules to protect your site, you can pre-emptively protect your site from being hacked.

FWS can do a lot of things (block DOS requests, show CAPTCHA verifications, block spam (via Akismet), and execute PHP plugins, for example) to protect your site. Further, it is fully configurable, so your imagination and the collective knowledge of our community is the only limit to ensuring that you are always 100% protected, no matter what software you use.

What are the requirements?

FWS requires PHP5 and ioncube. It does not use a database (though we may include an optional database-version in the future).

Who are the devleopers?

bfarber (co-developer of Invision Power Board) Put in alot of time developing key elements of the software.

Admin (author of CommunitySEO) is our main developer and will also handle support and upgrades.

Dan (Of controlc.com/aftervote.com ) runs the site and will handle general questions, marketing and sales.

FusE (PHP Dev) Will be doing support / Custom Rewriting / Installs and general dev.

Does the software use a lot of resources?
We hope not! Seriously though, the software has been written to be efficient as possible. The primary factor in determining the "load" our software may add to your overhead are the rules you configure. Naturally, the more complex and all-encompassing the rules you use are, the more resources the software will need to execute those rules. For instance, if you have the following rule only applying to specific $_GET query string keys. For users coming from CommunitySEO, the load should be equal to, or less than CSEO.



you will not use as many resources as the following rule applied to every single key of every single environment variable



Our rule packs (the ones we release officially) will be a continous work in progress. As new features and new issues with a software package are discovered, our packs must evolve to stay ahead of the game. We will strive, however, to ensure the rules we provide are as efficient as possible.

I have more questions!

Great! Post them in our Pre-Sales Inquiries forum and we'll be happy to assist.

Requirements

FireWall Script requires PHP5 and ioncube to run. ioncube loaders are included with the software, however there is still a possibility your host will need to load ioncube via php.ini, depending on the server configuration.

Our software does not use any database engine at this time.