With a server WITHOUT php mcrypt extension installed (or disabled).
Works, since it's not a Joomla requirement to have php mcrypt extension installed.
Fatal error.
Notice: Use of undefined constant MCRYPT_RIJNDAEL_256 - assumed 'MCRYPT_RIJNDAEL_256' in /path/to/joomla/libraries/fof/encrypt/aes.php on line 44
Notice: Use of undefined constant MCRYPT_MODE_CBC - assumed 'MCRYPT_MODE_CBC' in /path/to/joomla/libraries/fof/encrypt/aes.php on line 63
Fatal error: Call to undefined function mcrypt_get_iv_size() in /path/to/joomla/libraries/fof/encrypt/aes.php on line 90
Joomla 3.4.8/Joomla 3.5.0 RC4.
is mcrypt used elsewhere? or just for twoauth?
The JCrypt
API supports it and there's some functionality in the restore.php
upgrade file that uses it (but that checks for support and gracefully exits if unavailable). The password_compat
and random_compat
also make use of mcrypt internally in some conditions.
PHP mcrypt extension is not installed by default in some linux installations.
So i agree. IMHO it should exist a warning (warnings menu item in com_installer?) about that degraded experience and, of course, no fatal errors if it php mcrypt extension doesn't exist.
Eh, not so much there. Apparently that screen only has warnings related to extension uploads. Add something else to the system info page I'd say as that should be the appropriate place to put full environmental checks.
Labels |
Added:
?
|
Category | ⇒ | Installation Plugins |
Closed
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-03-23 17:40:58 |
Closed_By | ⇒ | brianteeman |
I'll do a patch to add a notice to the install app saying a degraded experience is available without mcrypt. For other uses of it, especially with the
FOFEncryptAes
class, itsisSupported()
method should be called first so things can degrade gracefully when the support isn't there.