Security

This is a Drupal module that provides support for Prowl, which is a push notification client for the iPhone. It relies upon php-prowl.

This module unobtrusively adds additional checkboxes to the permissions form located at admin/user/permissions - the additional checkboxes provide a much friendlier interface for dealing with the hundreds of checkboxes that accumulate on the permissions page as roles and modules are added to a Drupal installation.

On a test Drupal site I set up with 6 user roles, 105 core and add-on modules enabled, 9 content types, and the content permissions module enabled, there were 138 distinct permissions and 828 individual checkboxes on the permissions page. To initially set up the permissions to something sane, it took me about 17 minutes. On my first attempt of using this module after fully developing it, after wiping and restoring the database from a back up, it took me around 5 minutes to set up the same permissions. The point is that this module will save you time, especially on large sites.

Secure by Role is a simple Drupal module for shopping sites and others where security is important. When a page is requested, SecRole checks to see if the user is a member of a list of roles which should be only served pages over a secure connection (HTTPS). If this is the case, and the connection is not already secure, the user is redirected to the page they are requesting over a secure connection.

Why is this module's approach better than simply locking down your entire site behind a secure connection? Because not all the visitors to your site will be doing things which demand a secure connection. Search engine spiders, for example, are not going to be sending credit card details; they may even be incapable of indexing pages behind HTTPS connections. Or maybe they're simply human users who are just browsing with no intent to buy anything - yet. But with SecRole, you can easily configure the site so that, once these users create an account, they are served over a secure connection and their credit card details are safe. Your web server can avoid the overhead incurred by encrypting and decrypting data sent or received over a secure connection until it's necessary.

A state machine for paranoia, with the halting state typically entailing the implementation of a scorched earth policy response (i.e., erasing the Drupal database). Think DEFCON for Drupal.

This module is meant primarily for "paranoid" Drupal use cases involving information warfare. Typical users might be political dissidents in repressive regimes, BitTorrent bootleggers, various kinds of activists, and so on and so forth.

Basically, if you have adversaries trying to hunt & shut your site down or limit your ability to disseminate information, you'll probably want to install Lockdown to help maintain tight information discipline as well as to guard the perimeter and perhaps give you some advance warning when it's getting to be time to move shop.

This module allows user to move content (nodes) to trashbin. It inserts "Move to trash" button on node edit page, for users who have permission to move this node to trash.
What is trashbin then ? It's for you to decide. This module was made as simple as possible, providing minimal interface on it's own, but serving as bridge module for other modules at the same time. It provides hook which is invoked when user presses "Move to trash" and confirms the action.

This module became obsolete, because Flag module now has access control built-in. You can do same things with the Flag module

This module allows you to set up access to the site on base of request referrer, remote IP address or User Agent with reverse-lookup check of domain name (for searchbots)