Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79568 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40938 invoked from network); 11 Dec 2014 10:11:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Dec 2014 10:11:08 -0000 Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Linux 2.6 Received: from [82.113.146.227] ([82.113.146.227:49169] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/41-32494-ABD69845 for ; Thu, 11 Dec 2014 05:11:07 -0500 Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 113C110D567; Thu, 11 Dec 2014 10:11:01 +0000 (GMT) Date: Thu, 11 Dec 2014 10:10:58 +0000 (GMT) X-X-Sender: derick@whisky.home.derickrethans.nl To: Andrea Faulds cc: Remi Collet , internals@lists.php.net In-Reply-To: <648FEBB3-9D71-4AE3-BFDA-5ED268FC02A7@ajf.me> Message-ID: References: <5487E91D.6070602@fedoraproject.org> <648FEBB3-9D71-4AE3-BFDA-5ED268FC02A7@ajf.me> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1317091508-1418292661=:4080" Subject: Re: [PHP-DEV] libmcrypt: abandonware? From: derick@php.net (Derick Rethans) --8323329-1317091508-1418292661=:4080 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE On Wed, 10 Dec 2014, Andrea Faulds wrote: > > On 10 Dec 2014, at 06:33, Remi Collet wrote: > >=20 > > Having a dead upstream for crypto API is a critical issue :( > >=20 > > FYI some downstream (ex RHEL) don't even provide this library.=20 > > Already too much crypto libraries, and it will be a mess to provide=20 > > a dead project in an Enterprise distribution. > >=20 > > So php/mcrypt also not available. > >=20 > > But most applications. which use it, usually have alternative, and=20 > > make it optional (ex phpMyAdmin 4.3 now even use openssl as first=20 > > choice). > >=20 > > We probably have enough crypto API in PHP, and we probably should=20 > > mark this one as deprecated / unmaintained in 5.x, and move it to=20 > > PECL (7.x). >=20 > It=E2=80=99s my understanding that ext/mcrypt is quite widely used. Would= it=20 > not be possible to update the lib to use OpenSSL or something on the=20 > backend, so existing applications would not need changing? I think you're going to find this difficult, as the mcrypt=20 implementations can have some odd quircks in them. As the "maintainer"=20 of this extension I'd say to just drop it in PHP 7. I wouldn't even=20 bother trying to make it compile for it. cheers, Derick --8323329-1317091508-1418292661=:4080--