Message Board

Newbie/Basic Questions

Older Posts ]   [ Newer Posts ]
 Differences between script versions/languages
Author: C.Sturm   (26 Dec 08 10:35am)
Hi,

I wanto to know if there are differences between the honeypot scripts regarding performance or features.
 
 Re: Differences between script versions/languages
Author: M.Prince   (26 Dec 08 9:50pm)
Honey pot scripts all basically perform the same way. We tend to develop in PHP so the PHP version of the script is usually the most feature complete. Right now the following three types of honey pots have slightly more features than the others:

PHP
Perl
ASP .NET

The other honey pots will still work, they just don't support POSTing back to themselves so they aren't quite as good at trapping comment spammers.

To be clear, honey pots are for data gathering and we hand out official versions through our site. If you want to use the data we generate to block suspicious IPs from your website you need to use a script, plugin, or application that takes advantage of http:BL. For http:BL scripts, they are all developed by different authors to take advantage of the http:BL data feed. As a result, they all have different feature sets and flexibility. We recommend that all http:BL scripts support at least the following three things:

- An ability for the individual website to choose the characteristics of the IPs blocked (what types, what threat level, how stale)
- An ability for individual websites to whitelist specific IPs
- An ability to easily include links to a honey pot from pages served by the web server (in order to help generate more data for the Project)

While those are our recommendations, there is no requirements that http:BL script authors support any of the above. Check with the individual implementation to see the features it supports.

Matthew.



do not follow this link

Privacy Policy | Terms of Use | About Project Honey Pot | FAQ | Cloudflare Site Protection | Contact Us

Copyright © 2004–25, Unspam Technologies, Inc. All rights reserved.

contact | wiki | email