Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82153
Return-Path: <leight@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 12671 invoked from network); 8 Feb 2015 17:33:04 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 8 Feb 2015 17:33:04 -0000
Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.171 as permitted sender)
X-PHP-List-Original-Sender: leight@gmail.com
X-Host-Fingerprint: 74.125.82.171 mail-we0-f171.google.com  
Received: from [74.125.82.171] ([74.125.82.171:64874] helo=mail-we0-f171.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 8B/C5-15550-FCD97D45 for <internals@lists.php.net>; Sun, 08 Feb 2015 12:33:04 -0500
Received: by mail-we0-f171.google.com with SMTP id k11so22699681wes.2
        for <internals@lists.php.net>; Sun, 08 Feb 2015 09:33:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=MJU3OdjO3Bsi3TfSfTu3zDZAK0lIuZAZPE4SIeIUCb4=;
        b=Q4mauVmOf0CfAVmZPnO4wFxZq3024zBiuKbEPGq2nTTf8EHzH5z8JfmNeCKiCkKQEi
         vLVqFjd+ttQm1TqLzzdroM62JJb4fyTuJxNCE0mzPfgiVhPnxDgGRnsSr4aYs50yTKNr
         /L0NjwPCeWf4z17LxwuU6RdLpKROAwd3OILgbh9SBFo+szoR+UvrPdzG9aN6PFjoEznr
         FW11CIfOFEFjrR81k8Ul3llAKO9/BW2harZpleuVGYrMoH5j/O5zqm6GC//vfDzjKR68
         hg0+3UY766lCXPPTKekeQ9dFZjHjV2U6goWcwKe0kjKMgQZG5lOCC8erPlXarov1ttcb
         Qksg==
MIME-Version: 1.0
X-Received: by 10.180.76.133 with SMTP id k5mr26356318wiw.30.1423416780108;
 Sun, 08 Feb 2015 09:33:00 -0800 (PST)
Received: by 10.216.50.139 with HTTP; Sun, 8 Feb 2015 09:33:00 -0800 (PST)
In-Reply-To: <CAEZPtU5MR=6E86DfriM-Xo6bue6cTmcxBBv1yGd41-RwFmGKWQ@mail.gmail.com>
References: <D0FBCF22.5D217%fsb@thefsb.org>
	<CAGa2bXavqvp5St5in4ckWamVO8GcpkBqH2KOXATLkaFrQa7t0w@mail.gmail.com>
	<D0FCE2B2.5D254%fsb@thefsb.org>
	<CAEZPtU5MR=6E86DfriM-Xo6bue6cTmcxBBv1yGd41-RwFmGKWQ@mail.gmail.com>
Date: Sun, 8 Feb 2015 17:33:00 +0000
Message-ID: <CAPwsocF3qWL2zVgBrtOQH4=ZxBvhVYf2JiOxbV2NYa1Utj0aMQ@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Tom Worster <fsb@thefsb.org>, Yasuo Ohgaki <yohgaki@ohgaki.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Security changes in PHP 7
From: leight@gmail.com (Leigh)

On 8 February 2015 at 17:03, Pierre Joye <pierre.php@gmail.com> wrote:
> I agree with Derick about wrapping ext/mcrypt around OpenSSL or other to
> keep it around for BC. I simply do not have the resources to make that
> happen so someone has to jump on it (Derick?)
>

Are we happy to accept that we'll lose access to some of mcrypts
ciphers if we do this? I'd suspect most real world usage of php-mcrypt
is to implement AES anyway, so most users would be covered.