Need an explanation if settings fail (example : bad encryption key)

Hello,

Thanks for the real_aes Module.
I am the maintener of the dbee → module, that use encrypt module and may use the real_aes module.

• On the encrypt module project page, we can read that the real_aes module v7.x-2.x (latest stable branch) is not compatible with the encrypt module and we should use the v7.x-1.x version.
• But the v7.x-2.x version requires the encrypt module.
• Beside, there is no alert to the end user informing that the encrypt module won't work with this version of the real_aes module.

There is many ways to solve this.

1. The best way would be to fix the v7.x-2.x compatibility with the encrypt module
2. Or remove the encrypt dependency from the real_aes.info file
3. and/or throw on alert on the encrypt admin page if choosing the v7.x-2.x real_aes encryption method.

About the uncompatibility between encrypt module and the real_aes module v7.x-2.x:
Seems that the encrypt function returns an empty string.
Digging into this issue, I found that the cypto function throw an exception : Bad key length. But setting manually a 256bits key does not solve it.