Security

LAuth is a protocol to authenticate HTTP requests.

There are three actors in LAuth. A CLIENT needs to have access to a USER's resources on a SERVER.

The goal of LAuth is to enable servers to verify the identity of a client acting on behalf of a user without the user having to give to the client the secret he shares with the server.

What does this mean?

For example, let's say Alice have uploaded photos on photos.example.com, using a login name and a password that give her access to the whole range of services offered by photos.example.com.

Menu Access Override provides a configuration option to menu items to allow them to be displayed regardless of a user's access rights. This does not override any access control, it only overrides the display of the menu item. Useful for making sure links to members only pages are visible, but present a user with a login screen or other prompt to join.

Path403 seeks to provide an easily configured mechanism for providing custom access denied messages based on the path that users attempt to access. It can also optionally show a login prompt to anonymous users.

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

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

This module can be added to a site where CiviCRM is using an onsite payment processor. It protects against a data caching issue which causes billing information to be retained in CiviCRM's civicrm_cache table.

You shouldn't need this module any more. Upgrade to a recent CiviCRM instead.

See also -

• CiviCRM v4.1.3 release announcement
• Blog post on CCCCCC

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

When Cryptolog is enabled, Drupal 8's Drupal::request()->getClientIP() and Drupal 7's ip_address() output a 128-bit HMAC of the client IP address (in IPv6 notation), using a salt that is stored in memory and regenerated each day.

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

About the project

This module is 3rd party integration with Tor (anonymity network).
You have to be Drupal developer to use this module.

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: