4 ms·
Deprecating mcrypt this way is clearly a mistake regardless of how ineffective it is as an extension or how unmaintained it is. Almost every framework I've seen
by joesmo 10y ago
Deprecating mcrypt this way is clearly a mistake regardless of how ineffective it is as an extension or how unmaintained it is. Almost every framework I've seen makes use of it. In almost 9 years, it was not communicated to the community at all that this was based on unmaintained, buggy code, and now they just want to yank it in a minor upgrade? WTF? At the very least, there should be collaboration with people who maintain frameworks that use mcrypt as pretty much every major framework (ZF, Symfony, Laravel, etc.) does. This should be done in a major version upgrade like the one that just happened.
- CiPHPerCoder 10y agoThe release process specifically allows an extension to be deprecated and then punted to PECL. As for frameworks, I and others have already been going around (for years before the mcrypt deprecation came up) switching things to use OpenSSL (and, for that matter, authenticated encryption) instead of mcrypt. https://paragonie.com/blog/2015/05/if-you-re-typing-word-mcrypt-into-your-code-you-re-doing-it-wrong https://paragonie.com/blog/2015/05/if-you-re-typing-word-mcr... To date: ZF, CodeIgniter, Symfony, Laravel, and CakePHP all support OpenSSL instead of Mcrypt, as do many, many more. You get E_DEPRECATED in 7.1 then in 7.2 you can still pecl install mcrypt ...if you really have a need to support abandonware.