Security

Say you want users of your site to be able to upload and download documents, but you also want these documents to be protected in case someone breaks into your server. This module allows Drupal to encrypt files that users upload and decrypt files for download, keeping the unencrypted versions of files from ever being stored on disk. It does this by creating a custom file stream wrapper that Drupal can read from and write to and a new download method that sits alongside the regular public and private methods. So you can make Encrypted Files the default download method, or only use it as the download method for specific file-type fields.

Features:

• Uses AES-256 encryption via the AES module.
• Uses two symmetric keys for encryption by default.
• Provides two fields that you can add to your entities: one that stores files using site-wide encryption keys and one that stores files with a user-supplied password.

Dependencies:

• AES Encryption

Nota bene:

The idea of this module is to provide the ability to encrypt files and store them in the server and later decrypt them when needed.

This module compliments more popular and better known Login Toboggan and Login/Logout Destinations. It performs similar functions, but is specifically targeted at sites, running Spaces and Organic Groups.

The typical use of Spaces and Organic Groups is to segregate sections of the site and associate users with these sections. It is not unusual to use Spaces and Organic Groups to create an appearance of multiple, independently running sites on top of single Drupal deployment. In doing so, site owners often encounter a problem, related to user's login/logout experience: the standard Drupal implementation takes users to user's profile page upon login and takes to the home page of the overall site upon logout. This module provides a feature, which, if enabled within given space and organic group, alters the flow as follows:

a. The user visited a page within the organic group and he/she is not logged in, while the page requires login. After successful login the user is taken to the home page for the space/group.

b. The user is logged in and clicks the logout link on a page within the organic group - after the logout she or he will be taken to the home page for that organic group.

This module enhances the TAC lite module to enable the use of entityreference fields both inside and outside of field collections.

The aim of this module is to provide a set of tools to the administrator
that analyze Drupal's watchdog log records, identify and analyze patterns and provide intelligent suggestions to the site administrator.

Drupal's watchdog records logs are one of the most important sources of highly useful insights for any Drupal site administrator / developer. Though Drupal has a decent log viewer for the same, most of the time, we often have to rely on the experiences, senses and large amounts of patience of an expert administrator to systemmatically parse/classify records, identify patterns and make insightful interpretations / judgements from that usually huge volume of watchdog log records.

This module aims to help both the novice and the expert in this regard.

This module allows your website to comply with the Dutch law on the use of
cookies. By Dutch law the visitor must consent with placing cookies on your
client to gather visits or other information about the visitor. The site
owner must inform the visitor about what kind of information will be
gathered and must be able to provide proof of visitors’ consent.

The Dutch government provides a javascript-based solution that displays a
bar on top of the website. This bar provides all necessary elements to
comply with the law, like asking for permission and providing information,
except for actual disabling of cookies and tracking scripts.

This module uses the javascript solution from the Dutch government as a
library and adds the ability to prevent modules from placing tracking
cookies on your client. The main module offers the basic functionality
like showing and configuring the cookie-bar. To exclude certain
functionalities, submodules are used. Currently there is a submodule
for Google analytics, Piwik and Webtrends. These submodules make sure
their javascripts are not being executed, and their cookies are not being
set, when the visitor has not agreed. Users can always change their choice;
the module provides a link so visitors can change their mind. If cookies
were already set at this point, the module will delete them.