Message Board

Newbie/Basic Questions

Older Posts ]   [ Newer Posts ]
 Integrating Project Honey Pot with Drupal
Author: N.Hoeller   (27 Dec 12 12:00pm)
I run a multi-domain Drupal environment (one code base supporting multiple domains). I successfully had Project Honey Pot create a script for one of the domains, installed it in the Drupal base directory and was able to activate the script. I assume that I need to create a new script (with a different name) for each domain since the script is tied to the domain name.

A few questions.

1. Where have other Drupal sites installed the Project Honey Pot script and why? I found a forum post where the script was installed to /usr/lib/cgi-bin.

2. What is the best way to embed the link to the script in Drupal pages? By default, I 'escape' any HTML code for all but a few specialized pages. My CSS is a bit rusty, but I think I can add a new menu item in the footer (probably first or last) and suppress display based on the associated class or id.

Suggestions welcome!
 
 Re: Integrating Project Honey Pot with Drupal
Author: N.Hoeller   (29 Dec 12 11:49am)
I ended up adding a link to the script in my Footer menu, specifying a weight of 50 to ensure that it was at the end. I then used CSS Injector to make the link not displayable using one of the two CSS definitions below (for some reason, the ID of the footer was different on one of my Drupal sites).

#block-menu-menu-footer li.last {display: none;}
#block-menu-menu-footer-menu li.last {display: none;}

I also added the scripts to robots.txt in the Drupal base directory so that seach engines would not pick them up.

 
 Re: Integrating Project Honey Pot with Drupal
Author: H.User1325   (29 Dec 12 2:26pm)
To make sure you apply the correct weight to my comments, I have no knowledge of drupal implementation. With that, jumping in with both feet two thoughts.

I'm sure public honey pots on each of your domains will help the cause giving more options for QuickLinks, but that is not necessary from your standpoint. You can seed links to the one HP in all the domains you control.

Again not knowing how the script for {display: none;} is implemented, I would check the html generated to assure the HP link is included, but not visible. Obviously if the (not visible) link is not included in the html sent to the client, a harvester can't follow it to the HP.

I located my honey pots in sub-directories that I don't want well behaved search engines to index anyway, like cig-bin. I put another in with all the php scripts for a phpBB forum. So there is not hp entry in robots.txt, but its covered.

Lou
 
 Re: Integrating Project Honey Pot with Drupal
Author: N.Hoeller   (1 Jan 13 2:49pm)
Lou, thanks for the response! I decided to request a separate script for each domain to assist in tracking activity by domain, although I am not sure I can get that level of detail from the Project Honey Pot databases.

I will explore moving the script to cgi-bin - since Drupal processes all httpd requests, I was not sure how it will respond if the target is outside of Drupal's base directory.

I did a 'View source' on the Drupal pages and verified that the hidden link to the Project Honey Pot script is there.
 
 Re: Integrating Project Honey Pot with Drupal
Author: H.User1325   (1 Jan 13 3:51pm)
N.H. with all the HPs in a single account the data is an aggregate. When you get an ata boy email for helping identify a new harvester, which HP they used is identified. But yes, that is the way I did it too, one HP/domain.

Hmm, again no Drupal experience but as you can see the HP link is just an html anchor to an external page and not really processed by the server, just passed to the user's browser to "display". Actually scraped by the harvester's tool and the URL is followed later.

 
 Re: Integrating Project Honey Pot with Drupal
Author: N.Hoeller   (13 Jan 13 9:52am)
Lou, having multiple honey pots might also confuse spammers if they are targeting multiple domains on the same server. Many of my domains have links between them - I will see the same IP address hop from one domain to the next.

I am starting to see 'bad events' reported on my Honey Pot dashboard and have been able to track the spammers through the Apache logs. The next step is to implement the http:BL code and stop the really bad apples from even getting to the site. Or even better, figure out a way to redirect them to a safe site where sapmmers can play (and be tracked) without affecting my users.
 
 Re: Integrating Project Honey Pot with Drupal
Author: D.Zerkle   (18 Mar 13 1:04pm)
The standard Drupal install wants to manage all requests to your site. Almost everything, even 404 pages, gets handled by Drupal's index.php file.

If you want a honeypot to exist in a separate directory, you have to modify your root .htaccess file to allow requests to those directories go through. Put in the final rewrite rule for this BEFORE the standard Drupal rewrite rule (which directs everything to index.php). If not, all your honeypot pages will be Drupal 404 pages.
 
 Re: Integrating Project Honey Pot with Drupal
Author: A.Simmons2   (17 Apr 13 11:56am)
I'm toying with the same problem. Installed the httpbl.module, but there's no clear guidance on creating a honeypot within drupal. It does seem like the most sensible thing is to put the honeypot elsewhere on the filesystem.

I'm just wondering if it really matters if the honeypot is on the same domain as the drupal site, or whether putting it on its own subdomain would be just as effective. I do have some static html sites on sub-domains already, so I could pop them in amongst real content.

It seems to me that the helpful thing is simply contributing a honeypot.
 
 Re: Integrating Project Honey Pot with Drupal
Author: H.User1325   (17 Apr 13 2:26pm)
Putting the Honey Pot in a different domain or sub-domain is not a problem. If you think about it a QuickLink, is in effect, a link to a Honey Pot in another domain. They were developed for those people that want to help but can't add a script, to their domain because of rules there host has.

Do keep in mine you can only have one HP per domain or sub-domain, but any (all) webpage can links to each HP no matter which domain they are in, including QuickLinks.

For example, I manage several domains and a sub-domain. Each has a HP installed. Peppered through each webpage on all domains, including a forum, are random links to each HP. Works fine.

Good Luck.



do not follow this link

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

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

contact | wiki | email