Re: [RFC][VOTE] Deprecate then Remove Mcrypt Closed (23-6)
| From: | Davey Shafik | Date: | Fri, 02 Sep 2016 15:18:23 +0000 |
| Subject: | Re: [RFC][VOTE] Deprecate then Remove Mcrypt Closed (23-6) | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95573@lists.php.net to get a copy of this message | ||
I would still be OK adding this in RC2, TBH. I didn't realize it was
missed, and it's something we _need_ to do.
- Davey
On Fri, Sep 2, 2016 at 8:08 AM, Leigh <leight@gmail.com> wrote:
> On 22 March 2016 at 17:00, Scott Arciszewski <scott@paragonie.com> wrote:
> > Hi all,
> >
> > https://wiki.php.net/rfc/mcrypt-viking-funeral
> >
> > The tally of closing (2016-03-22T17:00:00) is 23 Yes, 6 No. This is a
> 79.3%
> > favorable response, which exceeds the 2/3 majority by a significant
> margin.
> >
> > Thanks to everyone who voted or participated in this discussion.
> >
> > I've heard and respect some of the objections raised by folks who voted
> No,
> > but moving this liability out of the core into PECL as soon as possible
> is
> > not only a good move for the security of PHP applications, but now we
> know
> > it's the choice the community wants.
> >
> > As promised, I'll get the E_DEPRECATED patch written soon.
>
> As we're now at RC1, I assume it is too late to push forward with this?
>