Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79533
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <5487E91D.6070602@fedoraproject.org>
Date: Wed, 10 Dec 2014 18:31:24 +0000
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <648FEBB3-9D71-4AE3-BFDA-5ED268FC02A7@ajf.me>
References: <CAPKwhwsOZiGPkvEtXYCBX3dJP3SJ=PTrwqRtQWVzX3SegK6jsg@mail.gmail.com> <5487E91D.6070602@fedoraproject.org>
To: Remi Collet <remi@fedoraproject.org>
Subject: Re: [PHP-DEV] libmcrypt: abandonware?
From: ajf@ajf.me (Andrea Faulds)

Hi!

> On 10 Dec 2014, at 06:33, Remi Collet <remi@fedoraproject.org> 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.
> Already too much crypto libraries, and it will be a mess to provide 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
> make it optional (ex phpMyAdmin 4.3 now even use openssl as first =
choice).
>=20
> We probably have enough crypto API in PHP, and we probably should mark
> this one as deprecated / unmaintained in 5.x, and move it to PECL =
(7.x).

It=E2=80=99s my understanding that ext/mcrypt is quite widely used. =
Would it not be possible to update the lib to use OpenSSL or something =
on the backend, so existing applications would not need changing?

Thanks!
--
Andrea Faulds
http://ajf.me/