Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91680
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1458063647.1202380.549998114.3D69249B@webmail.messagingengine.com>
References: <CAKws9z3rUE5+v+H_odY98=SKRvtwjLCtd1XHbhkHtxpC_G=PZA@mail.gmail.com>
	<CAH-PCH5zvY_im+zh6cjUjGYZo+fk2ubeg2LWe1pUM_fHf+2JnA@mail.gmail.com>
	<CAKws9z0dra7Mz7HnZ3RCqJ3b=7Ob9OSj__fe3CUEE5QhK1N8ZQ@mail.gmail.com>
	<CAH-PCH6gygwqcUGfV4G8aqYKysBmLqnuEjV3A2MJNWjQesprbA@mail.gmail.com>
	<1458063647.1202380.549998114.3D69249B@webmail.messagingengine.com>
Date: Tue, 15 Mar 2016 17:47:52 +0000
Message-ID: <CABHuAWxRuN0i0YO66ThJHHFEp0q5hBRCupS6kMLwDej-jzwfGg@mail.gmail.com>
To: Will Fitch <willfitch@php.net>
Cc: Ferenc Kovacs <tyra3l@gmail.com>, Scott Arciszewski <scott@paragonie.com>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b3a87d61a4cbe052e19ffeb
Subject: Re: [PHP-DEV] [RFC][VOTE] Deprecate then Remove Mcrypt
From: t.carnage@gmail.com (Chris Riley)

--047d7b3a87d61a4cbe052e19ffeb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 15 March 2016 at 17:40, Will Fitch <willfitch@php.net> wrote:

>
>
> On Tue, Mar 15, 2016, at 12:18 PM, Ferenc Kovacs wrote:
> > On Tue, Mar 15, 2016 at 6:13 PM, Scott Arciszewski <scott@paragonie.com=
>
> > wrote:
> >
> > > On Tue, Mar 15, 2016 at 1:09 PM, Ferenc Kovacs <tyra3l@gmail.com>
> wrote:
> > >
> > >>
> > >>
> > >> On Tue, Mar 15, 2016 at 5:11 PM, Scott Arciszewski <
> scott@paragonie.com>
> > >> wrote:
> > >>
> > >>> Hi PHP team,
> > >>>
> > >>> I've opened the vote on
> https://wiki.php.net/rfc/mcrypt-viking-funeral
> > >>> which aims to deprecate ext/mcrypt in PHP 7.1 then remove it in 7.1=
+1
> > >>> (i.e.
> > >>> make it only installable via PECL).
> > >>>
> > >>> In the interim, I'll be developing a (MIT licensed) decryption-only
> > >>> userland implementation of the mcrypt ciphers so people can migrate
> their
> > >>> code towards something better.
> > >>>
> > >>> This vote is opened on March 15th, 2016 and will close March 22th a=
t
> > >>> 17:00
> > >>> UTC.
> > >>>
> > >>> (Sidenote: Apologies for the brief unannounced hiatus from
> participating
> > >>> here.)
> > >>>
> > >>> Scott Arciszewski
> > >>> Chief Development Officer
> > >>> Paragon Initiative Enterprises <https://paragonie.com>
> > >>>
>
> In the RFC:
>
> "Removal from core: The following major/minor version (7.2.0 or 8.0.0)"
>
> and then
>
> "Vote =E2=80=9CYes=E2=80=9D to raise an E_DEPRECATED notice in PHP 7.1 wh=
en any mcrypt
> function is used and to remove the extension from core in 7.1+1."
>
> Which one is it? I feel removing at 7.2 would be too soon.  I agree that
> the abandonware is a nuisance, but many developers using ext/mcrypt have
> no idea of this.  Raising an E_DEPRECATED in the next 7.1.x, then
> removing in 7.2 is just too soon.
>
>
I disagree. It's not like we are obliterating the functionality from the
face of the planet, any user requiring mcrypt in 7.2+ can fully aware of
the consequences, install it from PECL. Also, bear in mind that some linux
distros (RHEL) have already dropped mcrypt support.

--047d7b3a87d61a4cbe052e19ffeb--