Home › Blogs › Christoph C. Cemper's blog
Drupal

Anti Proxy Hack drupal module

<< Drupal Anti Proxy Hack alpha test | How Drupal does Harakiri (aka Kill Itself) >>
Sun, 08/19/2007 - 23:57 — Christoph C. Cemper

Dan Thies’ recent post about the black hat SEO tactic to boot sites out of the google search results needs webmasters to act soon.

In fact my own company website suffers from such an attack and Google’s inability to detect the proper owner of the content (altough I had that copy up 2 years already, some scummy proxy sites can outrank me… thanks for that Google, stop bitching about paid links and fix your engine!)

Dan announced a Wordpress plugin, and as I’m affected myself I started the Drupal project “AntiProxyHack” to provide the functionality needed as protection against these attacks to the whole drupal community.

You should be able to download that plugin for 5.x in about 1,5 weeks from now…

Average rating
 
 
 
 
 
(1 vote)

Similar entries

  • Drupal Anti Proxy Hack alpha test

    The alpha version of the anti proxy hack module is available…

  • OpenSearch and why it rocks

    OpenSearch API let’s you free yourself from Google to some extend…

  • Wordpress blog hack rampage

    I received an abnormal high number of signals and messages from people abandoning their Wordpress blogs,

    because of their hacks, just like Fridaynite did .

    It appears to me that simply because there are so many vulnerable Wordpress installations out there, it became a promising goal

    to hack Wordpress installs and

    • inject some HTML code (for links)
    • inject WHOLE POSTS into the wordpress archives (backdated)
    • put in some cookie-stuffing code in to overwrite affiliate links’ credits

  • IBM Tutorials for Drupal

    As I mentioned in my recent post about Google, IBM & Co supporting Drupal IBM really adopted Drupal as a strategic base. cool thing is that their developerZone started publishing great tutorials about building with Drupal Getting started with Drupal…

  • Drupal6 is here - why we're not upgrading...

    So DRUPAL6 was released last week finally – this is the GO for all module developers (like us) and heavy drupal users (like us)

    to set aside their “normal” business (which is NOT drupal maintenance, consulting or else) and plan for DOZENs of hours and days

    to upgrade all their sites…

    Frankly,

    we are running DRUPAL 4.x sites

    we are running DRUPAL 5.x sites

    and we will be running the new company site for cemper.com on Drupal 6 soon (postponed launch for DP6)

    BUT, I will not and cannot commit to an upgrade mania solely to generate work and say we’re running recent versions