Protected Content

INTRODUCTION

The aim of Protected Content (proc) module is enabling client side encryption
and decryption of content. It allows for two modes of usage: stand-alone mode
and field mode. In stand-alone mode, the module provides forms for encryption and
decryption of files and text. In field mode, the module provides a field type for encryption and decryption of files and text from within any fieldable form.

REQUIREMENTS

OpenPGP.js v5.0.1

INSTALLATION

Install as usual. The crypto library will be loaded from its CDN.

FUTURE ROADMAP

Multiple signatures per content with recursive encryption.

LEARN MORE ABOUT PROTECTED CONTENT

Protected Content, Secure open source day - Haarlem (2019)

Protected Content: end-to-end PGP encryption for Drupal, Drupal Camp - Kyiv (2019)

Protected Content by Asymmetrical Client Side Encryption, Drupal Dev Days - Ghent (2022)

A pretty good content protection (Workshop), Drupal Con - Prague (2022)

SIMILAR PROJECT

Client-Side File Crypto

WARNING

Protected Content defines a zero knowledge proof protocol, based on the brain of its users. The passphrases defining private keys are not stored (and should not be stored) in any medium but the brain of their authors. I.e, a lost passphrase that allows for the decryption of a content no one else is a recipient of equals to a (hopefully) forever lost content. Use it wisely.
Protected Content tries not to be very opinionated. An exception is: you can only remove a recipient by updating a protected content if you are a recipient and the author of the content being updated. If you are a recipient and not the author, you can only add new recipients.