Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79542
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <648FEBB3-9D71-4AE3-BFDA-5ED268FC02A7@ajf.me>
References: <CAPKwhwsOZiGPkvEtXYCBX3dJP3SJ=PTrwqRtQWVzX3SegK6jsg@mail.gmail.com>
	<5487E91D.6070602@fedoraproject.org>
	<648FEBB3-9D71-4AE3-BFDA-5ED268FC02A7@ajf.me>
Date: Wed, 10 Dec 2014 19:37:36 +0000
Message-ID: <CAPwsocE+tc5aLwiTP51F2NDFGJvL5vsEO1TQ+UPT=_xApCFJ2Q@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] libmcrypt: abandonware?
From: leight@gmail.com (Leigh)

On 10 December 2014 at 18:31, Andrea Faulds <ajf@ajf.me> wrote:
>
> 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 ba=
ckend, so existing applications would not need changing?
>

Focusing on the "or something". What are our options outside of OpenSSL?

We could probably cover all of the features of mcrypt by compiling our
own library from a selection of proven public domain or GPL sources if
there is nothing that fits the bill exactly. That would give us the
flexibility to pick the features we want.

I wouldn't object to something a little more current in PHP 7 with an
mcrypt polyfill.

Crypto is a touchy subject though, so what are our options?