On 06/10/16 11:12, Jakub Zelenka wrote: > I don't think it can be added to PECL as it breaks its licensing rules > (mcrypt is GPL licensed):
It is already an established component in PHP and while it's use has been discouraged for a long time, simply switching it off will break a lot of legacy applications. It is not simply a matter of 'changing to a more modern alternative'. If an application has data stored by mcrypt, and it was a popular method of encoding passwords, then any migration path is going to need to provide a method of re-encoding that data while mcrypt is still available. There needs to be a proper migration guide to identify the secondary effects of pulling it although as has been indicated, many distributions will simply build it from PECL and carry on providing it, so the move only really impacts people who build their own installations ... and even there it's a simple exercise to restore anything relegated to the second level of code storage. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
