Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91675
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain paragonie.com designates 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH5zvY_im+zh6cjUjGYZo+fk2ubeg2LWe1pUM_fHf+2JnA@mail.gmail.com>
References: <CAKws9z3rUE5+v+H_odY98=SKRvtwjLCtd1XHbhkHtxpC_G=PZA@mail.gmail.com>
	<CAH-PCH5zvY_im+zh6cjUjGYZo+fk2ubeg2LWe1pUM_fHf+2JnA@mail.gmail.com>
Date: Tue, 15 Mar 2016 13:13:59 -0400
Message-ID: <CAKws9z0dra7Mz7HnZ3RCqJ3b=7Ob9OSj__fe3CUEE5QhK1N8ZQ@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11360400eb77c3052e198583
Subject: Re: [PHP-DEV] [RFC][VOTE] Deprecate then Remove Mcrypt
From: scott@paragonie.com (Scott Arciszewski)

--001a11360400eb77c3052e198583
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 thei=
r
>> code towards something better.
>>
>> This vote is opened on March 15th, 2016 and will close March 22th at 17:=
00
>> UTC.
>>
>> (Sidenote: Apologies for the brief unannounced hiatus from participating
>> here.)
>>
>> Scott Arciszewski
>> Chief Development Officer
>> Paragon Initiative Enterprises <https://paragonie.com>
>>
>
> hi,
>
> first some formalities:
> please make sure to follow the process stated at
> https://wiki.php.net/rfc/voting
> New RFCs first should be proposed for discussion and it would require a
> bit of vetting before it can be moved to the voting phase.
> I can see your thread "mcrypt extermination plan" but I can't find any
> mail linking to the rfc page before this one instantly moving it into
> voting phase.
> I would suggest cancelling the vote and waiting a bit(I would say 2 weeks=
)
> for any discussion/feedback on the rfc itself.
> Personally I also don't like going with the minimal one week voting perio=
d
> as it is too easy for somebody to miss the chance to vote because of
> vacation or just a busy week.
> =E2=80=8B=E2=80=8B
>
> I also wanted to mention that some of unsupported ciphers listed under
> https://wiki.php.net/rfc/mcrypt-viking-funeral#backward_incompatible_chan=
ges
> can in fact be supported by openssl as it(openssl) allows the usage of
> plugable engines.
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>



https://wiki.php.net/rfc/mcrypt-viking-funeral?do=3Drevisions <- already be=
en
under discussion for a while

=E2=80=8B> =E2=80=8BI also wanted to mention that some of unsupported ciphe=
rs listed under
https://wiki.php.net/rfc/mcrypt-viking-funeral#backward_incompatible_change=
s
 can in fact be supported by openssl as it(openssl) allows the usage of
plugable engines.

Can be supported !=3D=3D is currently supported out of the box.

Scott Arciszewski
Chief Development Officer
Paragon Initiative Enterprises <https://paragonie.com/>
=E2=80=8B

--001a11360400eb77c3052e198583--