Security

Confident CAPTCHAâ„¢ is a clickable, image-based CAPTCHA that stops spam and malicious bots, while remaining very easy for people to solve. All your website visitors have to do is click a few specific images to prove they are human and not a bot. It takes just a few seconds to solve.

Stop spam and bots on your website without frustrating your users. Download Confident CAPTCHA today!

This module enables a Drupal website to send statistics remote Zabbix server using a locally installed Zabbix client. For more information on Zabbix, see http://www.zabbix.org

The Zabbix server can then be configured to monitor the incoming statistics and trigger alerts according to your own specific requirements.

Gain a deeper understanding of your Drupal performance and find those transient problems before they become major issues.

The long name for this project could be: Static Code Analysis for Security Vulnerabilities.

Show CAPTCHA protection on selected forms after specified number of unsuccessful form submit attempts has been made.

Update Status Proxy is a module which provides a work-around for Drupal's inability to handle proxy servers, which makes getting the update status of modules impossible when your site is behind a restrictive firewall.

It works by providing a local endpoint which proxies the request through to the original source of the update status information, via a proxy server of the user's choice.

An implementation of the Content Security Policy specification.

This module has been abandoned in favor of the Security Kit module. See http://drupal.org/node/1109414 and https://drupal.org/node/1287834 for more information.

Overview

This module creates a 'superuser' role, and grants all permissions to that role. It also defines a new permission, 'administer software updates', which allows any user with the superuser role to run update.php without having to alter the $access_check (D5) or $update_free_access (D6) variables.

This module requires the Permissions API module.

This module adds support for mixed use of SSL and non-SSL (http and https protocols) for the 6.x branch of Domain Access.

Currently, Domain Access allows you to specify per domain whether to use http or https, and if a domain source is configured, URLs throughout that site (including form actions and so forth) use that protocol. However, if your site mixes use of both protocols (say, with SSL to protect the user login page, admin pages, or authenticated sessions in general), Domain Access does not support that configuration.

For background information, see the original issue: #758714: Allow both http and https for a given domain?

The Problem

As a Drupal developer, it's very likely that you have saved passwords for several of your websites. This makes it easier when coming back to it after a while. However, there are several situations where this is not desirable:

Enables a period of time to be set to throttle how often a password reminder email can be sent to each user.

This can be used to prevent a user being sent multiple password reminders by a malicious visitor that knows their username.

Sponsorship

• Initial development - BrightTALK

Development

• Developed by Henrique Recidive for Code Positive.