Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90464
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender)
To: internals@lists.php.net
References: <CAKws9z1g24rD=t92+9xKtO=3PuwQ3_N=L36gmVMqCC84CoqipQ@mail.gmail.com>
 <CAEZPtU7-Lk=jGsTQgRZOvBpcPPgdX3V-23=3_k9CXbmxU77V1A@mail.gmail.com>
 <CAKws9z248Kj=0qTLPZik0Ki1_zGPq+4fr6HQi_keeVCso1S4eQ@mail.gmail.com>
Message-ID: <5692CDB6.5050905@gmail.com>
Date: Sun, 10 Jan 2016 21:31:34 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <CAKws9z248Kj=0qTLPZik0Ki1_zGPq+4fr6HQi_keeVCso1S4eQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Libsodium
From: rowan.collins@gmail.com (Rowan Collins)

On 07/01/2016 16:11, Scott Arciszewski wrote:
> I'm personally not going to bother pushing
> for a pluggable crypto API if the only option is to use OpenSSL and
> all its legacy cruft.

I think what people are suggesting is not that libsodium shouldn't be 
supported under-the-hood, just that the fact you're using it shouldn't 
be exposed to userland. A PDO-like encryption interface (which as I 
understand it is not what you proposed in your other thread) would allow 
us to add libsodium in such a way that a relatively painless migration 
path can be created if it goes the way of mcrypt. So the pluggable API 
removes the need for any of the sodium_* / Sodium::* / \Sodium\* functions.

Regards,

-- 
Rowan Collins
[IMSoP]