Active
Project:
Encrypted Settings Field
Version:
7.x-1.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Apr 2011 at 15:04 UTC
Updated:
26 Oct 2011 at 20:50 UTC
This module should provide an additional encryption method: "AES (3rd party module)" or "Encryption (3rd party module". This should increase the security level of this field module.
Comments
Comment #1
danithaca commentedreferences:
http://drupal.org/project/aes (D7)
http://drupal.org/project/encrypt (D6)
Comment #2
theunraveler commentedActually, the Encrypt module provides hookable encryption methods itself. It would be awesome if this module could just implement the Field API parts, and rely on Encrypt for the actual encryption.
I might be able to write a patch a bit later.
Comment #3
mrfelton commentedsubscribing
Comment #4
theunraveler commentedFixed typo in title.
Comment #5
theunraveler commentedI'd like to propose that we just include this module in the Encryption module, as an additional module that the user can enable separately. In the 7.x-2.x branch of Encrypt, I just implemented an Encrypt Form API module that allows developers to encrypt things through the Form API. I think this module could work similarly, only through the Field API. It seems like a natural fit to me.
Also, I was thinking that there is no need to create a separate "encryptable" field type. Rather, each of the field types that Drupal defines by default should have the option of being "encryptable". This makes the module a lot cleaner, IMO.
I started a bit of work implementing some of this, but I'd like to know what you think about the idea.
Comment #6
danithaca commentedSure. Feel free to copy code to the Encryption module.
Comment #7
theunraveler commentedAwesome! Care to co-maintain Encrypt?
Comment #8
jakew commentedIs there any update on this? Is it available in the 7.x-2.0-beta1 release of Encryption?
Comment #9
theunraveler commentedNo, it isn't. I was hoping to put it in for beta2.