So, as I had a bit of time tonight, I dusted off the old coding fingers and dabbled with the zenHttpbl plugin. I did make a few minor changes (See Changelog) and I also moved the plugin to a GitHub repository.
What is zenHttpbl?zenHttpbl is my implementation of the Project Honeypot service into plugin form for Zenphoto. What the plugin does (before any theme data is sent) it references the browsing IP against the DNS Blacklist service provided by Project Honey Pot. It then returns a threat rating based on actions the IP has done maliciously (spamming, etc). The plugin then, based on the options you set, either allows the IP to browse the Zenphoto site as normal, or it will stop the IP from browsing by various methods.
So if a malicious IP attempts to access your site, not only will it stop them from accessing your site, it stops the traffic completely that would be generated from loading the pages.
DownloadDownload of the zenHttpbl plugin has been moved to a GitHub repository and can be located
hereChangelogv1.4.4.4
Version update after testing with 1.4.4.4 build.
Moved download to GitHub repository.
Added directions for testing the HoneyPot plugin.
Added redirect to QuickLink if specified and HoneyPot file not specified.
Ordered of redirect/exit in following priority. HoneyPot File -> QuickLink -> Exit()
Please feel free to respond if you have any questions or notice any errors.
Edit:
Sorry, I placed this under general and not plug-ins. -M
Comments
in admin/logs/security, I regularly see attempts to connect to my site.
attempts are blocked by zenphoto (I cross fingers to zenphoto don't have security holes).
is that this plugin will block access to the connection url to identified spammers ?
it will be a very good news and will enhance zenphoto security
btw, there was a ticket on bugtracker (I don't remerber ticket number) to implement a honeypot on comment post (a hidden field that allows to detect spammer if it is filled).
since this addition in zenphoto 1.4.4, I don't have spam at all (my akismet plugin seems redundant).
so if your plugin only allows to filter spamming, maybe your plugin is redundant too.
Btw, note for EU based users that sending (and possibly storing) IPs to US servers for checking can be a privacy and legal issue. Akismet for example is a bit problemtic in German law.
@vincent This is a bit different than an anti-spam plug-in like Akismet. By the time those plug-ins have checked to see if the IP is a spammer etc, your site has already served traffic (images etc) to the spammer. If any of that traffic contains email addresses, harvesters & spammers grab that info no problem. What the Project Honey Pot plugin does happens before any webpage traffic is sent to the user(or malicious bot). Then if the IP is in the database, it is then diverted to either a honeypot, or simply exits() the php call stopping the remaining traffic.
Could you link me to a good reference of the priv laws? When I google I get a bunch of blogs about Germany and the Facebook and Google stuff but no actual links to the laws.
The difference is that if you use OpenID or any other service to log in you do it yourself on purpose. If this honey pot does do this without the visitor knowing it is problematic.
Even all the social network buttons do sent cookies just on visiting a site with such a button, if you click or not (I made a plugin based on another script currently unrelease on my GitHub page). Also problematic as is Google Analytics for example.
We have strict laws here in the EU..;-)
I have an observation for acrylian and his paranoia on IP addresses. First, as I have said many times before, if the EU laws are as he says (I have not looked) then the internet itself is in violation: DNS servers in particular. Probably that is the case, I have often noticed that legislators write laws about things for which they know nothing, thus bollixing everything.
But back to the plugin. It does not send an a users IP address anywhere, so would not be in violation. It does send a transformation of the IP address, but that is not the address.
If the legislation prohibits sending 4 octet number sets then it it indeed quite expansive and overstepping. There are any number of legitimate uses for octet sets that some suspicious bureaucrat could decide was someone's IP address. If the EU will permit such laws to be valid then they well deserve that the Internet should not work for them.
Also, are you interested in trying it on the Zenphoto.org site to see if it eliminates the forum spammers? I'd bet that it drops the amount of spam drastically (I hope).
As my site has never had intense spam traffic, I haven't noticed a difference. However seeing the projecthoneypot dashboard I've blocked 2000+ visits since I implemented it.
It is not about using IP, it is about storing mainly.
Here is a lenghtly text about for example how to use the Akismet filter correctly:
http://faq.wpde.org/hinweise-zum-datenschutz-beim-einsatz-von-akismet-in-deutschland/
http://www.domainist.de/rechtliches/verwendung-von-akismet-plugin-rechtlich-bedenklich
Sadly it is German for the target group but maybe the Google translator will give you an idea. Not only that, it is a entired different system..;-)
Are these exempt from the law? (The article is a Wordpress interpretation, so may, as it says, not represent the real law.) So, Europe, feel free to enforce this law, you will just not get any content from the US. Or do not enforce the law. But if the law is not uniformly enforced then there is a serious issue with your legal system.
BTW, if DNS servers are exempt, then this plugin is also legal since it uses DNS to provide the information. See how slippery such laws are?
But it does not matter if you or I think these laws are slippery or whatever (There are quite few things in the US that look weird from this side of the pond as well..;-)). They exist and we or specifially EU citizens have to live with it (they had a weird idea about cookies as well that was even less practicable...I think that didn't get through - keyword bureaucracy)