easyfit (maintainer of AES) contacted me a couple weeks ago and we have been discussing our modules and goals.

We have decided that we have common goals of creating a module that provides an extensible encryption solution for Drupal. This means that we are going to try to combine our efforts into this module.

This thread is to get these thoughts out in the open and to start to talk about the details about this transition.

Comments

zzolo’s picture

Here are some of my initial thoughts on supporting the users of AES. Ideally we want to make it so that a user of AES can turn off their AES module and then jsut turn on Encrypt and it be seamless. This may not be possible, and if not, we need to create expliciti instructions on how to do that. Note that this does not encompass the user password functionality of the AES module (which I think should go into another module)

* We probably need to support the key that is in AES somehow. This may mean that we have to push through #573728: Utilize ctools plugins for key methods
* We also need to support the method that AES uses and create an encrypt method hook implementation. There may be more than one for this.
* We then want to think about people using the AES API. For a seamless transition, we will need to recreate aes_encrypt() and aes_decrypt() and can probably just make them wrappers around the encrypt() and decrypt() respectively.
* I believe there are other AES API functions that may need to be addressed.
* For supporting the AES functions, we need to determine how long we will support them. I would suggest just through the first major version (1.x). Also, on a technical note, I see an include in the hook_init that adds encrypt.aes.inc where we can put all this into one file.

zzolo’s picture

greggles’s picture

Version: 6.x-1.x-dev » 7.x-2.x-dev

As far as I can tell this is basically done from the perspective of the encrypt module. I think it should be up to AES to provide the upgrade path that would take care of the bullet points in #1.

If there are other features missing from Encrypt that AES needs then it would be great to get feedback on what they are.

greggles’s picture

Issue summary: View changes
Status: Active » Fixed

Updating based on #3. It seems like the AES module decided to not work on this.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.