Security

This module is 3rd party integration with Death by Captcha service.
You have to be Drupal developer to use this module.

Don’t let CAPTCHAs get in the way of your marketing goals! With Death by Captcha, you can bypass any CAPTCHA from any website. All you need to do is implement our API, pass us your CAPTCHAs and we’ll return the text. It’s that easy!

Death by Captcha Offers:

• A hybrid system composed of the most advanced OCR system on the market, along with a 24/7 team of CAPTCHA solvers.
• An average response time of 17 seconds, with an average accuracy rate of 90% or more. And you always pay for correctly solved CAPTCHA only!

Note

This is not official module of Death by Captcha.
So if you require any other information related to API, please check here:
http://www.deathbycaptcha.com/user/contact

Installation

1. Install module.
@todo

Requirements

You need to register an account in Death by Captcha.
And credit your Death by Captcha account by purchasing CAPTCHA packages.

Alternative solutions

Authors

This module integrates FuckItJS with your Drupal site.

If you have FuckItJS enabled you will never have to worry about your poorly written and/or untested Javascript breaking your client's site in production. FuckItJS transparently takes are of fixing your code for you.

For more information about FuckItJS, please visit the developer's site.

This module has hit a conceptual issue. Since the form_build_id changes throughout the lifetime of the form, there seems to be no way to identify a form such the user can't go back and submit it...

For a different approach, try
http://drupal.org/project/hide_submit or
http://drupal.org/project/block_submit

If there was a way to identify a form instance this module would provided two mechanisms to prevent forms being submitted twice
On the server side, there are form validate and submit callbacks to prevent the submit function running twice for a given form_build_id
On the client side the following javascript can be added to form buttons,
this.disabled=true,this.form.submit()

For site builders

A config page would allow admin to write the form_ids of affected forms

For module developers

In your form or form_alter function, you would call
submit_once_php(&$form);
or
submit_once_js(&$form);

Cryptolog enhances user privacy by logging ephemeral identifiers rather than actual client IP addresses in Drupal's database tables and syslog.

Once enabled in a site's settings.php file, Cryptolog replaces the PHP global variable $_SERVER['REMOTE_ADDR'] with an HMAC of the client IP address, using a salt that is stored in memory and regenerated each day.

Because Cryptolog uses the same unique identifier per IP address for a 24-hour period, it is still possible to do some statistical analysis of the logs such as counting unique visitors per day. In addition, unlike other solutions of setting $_SERVER['REMOTE_ADDR'] to either one static IP address or a completely random IP address, Drupal's flood control mechanisms still function as normal.

Drupal modules will submit the hashed IP address to remote services (e.g. a credit card payment gateway); therefore Cyptolog effectively anonymizes IP addresses sent to third-party services (aside from services which receive HTTP requests directly from the end user).

This module tracks downloads and warns administrators if someone is downloading too many files within a given timeframe.

Adds IP filtering authentication to end points created by the services module.

Global IP filtering settings can be set up in the admin at admin/build/services/rest_ip_filtering, but these settings can be overwritten on a per end point basis in the authentication screen for the end point.

Dependant modules:

• Services
• REST Server
• Autoload
• Chaos tools