Re: [RFC][VOTE][RESULT] Removal of dead or not yet PHP7 ported SAPIs and extensions

Hi David, On Tue, February 10, 2015 22:38, David Muir wrote: > >> On 10 Feb 2015, at 9:29 am, "Anatol Belski" <anatol.php@belski.net> >> > wrote: > >> >> Hi, >> >> >> the voting on the removals in PHP7 in hereby finished. The results are >> >> >> item yes:no >> >> sapi/aolserver 32:0 sapi/apache 32:0 sapi/apache_hooks >> 31:0 >> sapi/apache2filter 23:1 sapi/caudium 30:0 sapi/continuity >> 28:0 >> sapi/isapi 28:0 sapi/milter 10:9 sapi/phttpd >> 26:0 >> sapi/pi3web 24:0 sapi/roxen 23:0 sapi/thttpd >> 25:0 >> sapi/tux 25:0 sapi/webjames 25:0 ext/imap >> 14:19 >> ext/mcrypt 15:18 ext/mssql 17:13 ext/pdo_dblib >> 4:18 >> ext/sybase_ct 17:1 >> >> As most of the items are considered to be removed, the ones to stay >> untouched by the 50%+1 requirement are >> >> ext/imap ext/mcrypt ext/pdo_dblib >> >> I'm going to implement and tag the changes considered ASAP. Regarding >> > the >> stuff to considered to be removed from the core - if there are some >> supporters, the sources will be made available in the git tag. They can >> > be >> anytime ported to PHP7 and possibly resurrected. >> >> Regards >> >> >> Anatol >> >> >> >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > > Does this mean PHP will be taking on the role of maintaining libmcrypt as > well? If a security issue is found, what is the course of action? > not that I knew, libmcrypt is not maintained. An alternative were openssl probably. Regards Anatol