|
- Readme First! -
Read and follow the rules, otherwise your posts will be closed |
|
|
|
|
|
There are currently, 148 guest(s) and 0 member(s) that are online.
You are Anonymous user. You can register for free by clicking here |
|
|
|
|
|
|
 Fortress™ a premiere security application for any PHP website is steadily progressing with real world success at Nuke Cops™ and Computer Cops. The next release will build on the already award winning capability to stop annoying hackers. It will include cumulatively:
Alligators
BanOnDemand™
CSV Logging
HTML Logging
Fortress™ effectively replaces the old .htaccess bad bots code. Used with BanOnDemand™ and Alligators, applications that harvest websites not just for their content but for email addresses will steadily make Fortress™ an artificial intelligent application.
Our next release will give the owner/operator of a website the ability to educate Fortress™ on their terms. By supplying the Fortress™ HTML log for public viewing, harvesters will naturally lend to fetching the URLs that have been snared as attacks against your system. They will try to use those same attacks against you and will ultimately lead to a Fortress™ ban.
Fortress™ will now build its own list of not only hackers, but harvesters trying to gain email for SPAM, or even bandwidth stealers.
Fortress™ Benefits:
Stop SPAMMERS from data mining emails,
Stop bandwidth stealers from harvesting your site,
Intelligently build a ban list via fortress.htm,
No database connection is involved thereby ensuring no attacks can be injected thru Fortress™,
Triple Play intelligent work via fortress.htm, fortress.csv, and BanOnDemand™,
When a ban is enforced, they are fed to the Alligators,
Union Tap Code will sound the horn for Fortress™ to begin its magic.
Along with the next release of Fortress™ comes an updated Union Tap Code. In all forms of plaintext and Base64, Union Tap Code targets HTTP GET queries that contain the not so friendly database terms:
UNION
SELECT
DROP
DELETE
INSERT
TRUNCATE
UPDATE
Speed is on the forefront of these applications. Only necessary functions are used to ensure proper protection quickly. Your users won't even notice they are running.
|
|
Posted on Wednesday, May 12 @ 14:45:42 CEST by Zhen-Xjell |
|
|
|
|
| |
|
Average Score: 3.28
Votes: 7
|
|
|
|
|
|
|
| | The comments are owned by the poster. We aren't responsible for their content. |
| | | | |
| No Comments Allowed for Anonymous, please register | | | | |
Re: Fortress™ Status Update (Score: 1)
by JLMax on Wednesday, May 12 @ 15:28:09 CEST
(User Info | Send a Message) | THANKS NUKECOPS.....!!!
With your old fortress i'm singing every day... "Another one Bites the Dust"...
With this new package, we will sleep like babies.. |
| | | | |
Re: Fortress™ Status Update (Score: 1)
by zanis on Wednesday, May 12 @ 16:40:00 CEST
(User Info | Send a Message) | Please please release this soon!
Cheers
Zanis |
| | | | |
Re: Fortress™ Status Update (Score: 1)
by zanis on Wednesday, May 12 @ 19:17:31 CEST
(User Info | Send a Message) | Our next release will give the owner/operator of a website the ability to educate Fortress™ on their terms. By supplying the Fortress™ HTML log for public viewing, harvesters will naturally lend to fetching the URLs that have been snared as attacks against your system. They will try to use those same attacks against you and will ultimately lead to a Fortress™ ban.
That is a very very good idea! |
| | | | |
Re: Fortress™ Status Update (Score: 1)
by johny_rm on Thursday, May 13 @ 02:58:57 CEST
(User Info | Send a Message) | That sounds great!
I have one question, though: Will the search engine spidering be compromised in any way? |
| | | | |
Re: Fortress™ Status Update (Score: 1)
by dmolavi on Monday, May 17 @ 07:48:21 CEST
(User Info | Send a Message) http://www.nukedgallery.net | | not to sound like a prick..but what legal precidence do you have for trademarking "Fortress" and "BanOnDemand"? do you have the appropriate paperwork filed with the USPTO? if so, i'd be interested in the relevant URI's showing that the appropriate filings have been made. if not, there's nothing stopping someone from trademarking those terms then forcing you to stop using them. |
| | | | | |
