Here are the major items that I have in mind for the 7.x-3.x release:

  • Switch to using Key for key management
  • Remove default, basic encryption method
  • Move the MCrypt plugin to a separate module (prior 7.x.2.x releases must provide an upgrade path).
  • Remove extra code that provided backward compatibility with prior versions
  • Update tests for 7.x-3.x

The general idea is to bring the 7.x version to feature parity with the 8.x version currently in development.

Comments

rlhawk created an issue. See original summary.

spadxiii’s picture

spadxiii commented

Just a thought, but perhaps add support for the aes module?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

The aes module provides the same feature set as the encrypt module, but it has several differences in how it does that work which make it less flexible and less secure.

I think the only module we would want to integrate more closely is https://www.drupal.org/project/real_aes

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Status: Active » Needs work
Related issues: +#2849072: Mcrypt is deprecated in PHP 7.1, +#2942898: mcrypt extension is deprecated in PHP 7.1 and removed in PHP 7.2

This roadmap is over three years old and should be revised in light over recent developments regarding mcrypt (see related issues).

On the positive side, Encrypt is now integrated with Real AES.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Issue summary: View changes

Updated issue summary to reflect current plan regarding Mcrypt.

ptmkenny’s picture

ptmkenny commented
Status: Needs work » Closed (outdated)

Development of Encrypt for Drupal 7 has ended.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.