Closed (duplicate)
Project:
Real AES
Version:
8.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
22 Aug 2016 at 15:45 UTC
Updated:
20 Sep 2016 at 14:14 UTC
Jump to comment: Most recent
When I try to install the module , I get the following message:
Module real_aes doesn't meet the requirements to be enabled. [error]
Please install the Defuse PHP-encryption library via Composer. See README.txt (Currently using Defuse PHP-Encryption library version Not Installed)
The following libraries have been installed with the Composer:
Loading composer repositories with package information
Updating dependencies (including require-dev)
- Installing paragonie/random_compat (v2.0.2)
Loading from cache
- Installing defuse/php-encryption (dev-master 6aab2f4)
Cloning 6aab2f4df7605382685271e5658d2db61f37be1c from cache
paragonie/random_compat suggests installing ext-libsodium (Provides a modern crypto API that can be used to generate random bytes.)
Unfortunately it is not possible to enable the module
Comments
Comment #4
codefolder commentedComment #5
codefolder commentedOnce more reasonable:
1.) Installing "Composer Manager for Drupal 8" (https://www.drupal.org/node/2405811). ;-)
2.) Download the module with drush => drush dl real_aes
Result:
How can I solve the requirements in composer.json file? Or is the problem somewhere else?
Regards
Comment #6
rlhawkThis is related to #2727845: D8 - Update module to use Defuse PHP Encryption 2.0. Can you install d8_update_module_to-2727845-14-do-not-test.patch from that issue and see if it fixes the installation error?
Comment #7
codefolder commentedWith the installed patch from #comment-11521629 I get this error:
Comment #8
codefolder commentedIit looks to me like a problem with the "paragonie/random_compat" version from the Drupal Core (v. 1.4.1).
With the patch from "#2763787: D8 - Upgrade random_compat to latest version" and the latest patch from "#2727845: D8 - Update module to use Defuse PHP Encryption 2.0" I can enable the module.
But that would be only a temporary solution
Comment #9
nerdsteincodefolder, this is resolved with recently rolled changes to core 8.2.x and a patch recently rolled into the 8.x-2.x version of this module.
I'm marking this ticket as "Closed (duplicate)" since the other work done should resolve this with the 8.x-2.x branch (which we strongly recommend using).