Re: [RFC] Libsodium

From: Date: Sun, 10 Jan 2016 20:39:17 +0000
Subject: Re: [RFC] Libsodium
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On Sun, Jan 10, 2016 at 3:18 PM, Tom Worster <[email protected]> wrote:
> On 1/7/16 11:24 AM, Pierre Joye wrote:
>>
>> What I do not like too much is the addition of an extension with
>> (relatively) low level functions for one specific library. It does not
>> really matter how good is this specific library, I simply do not see
>> such addition as a good strategic move.
>
>
> I also worry that it's yet another thing to maintain. The more API you offer
> to the PHP programmer, the more responsibility you take on.
>
> Tom

Except two things:

1. I'm trying to get rid of mcrypt, bringing the net change of
cryptography libraries to maintain to 0, but still improving the
cryptography library availability significantly.
2. I'm willing to maintain it, so you're gaining manpower with this change.

I'd argue that, strategically, what I've proposed across several RFCs
is superior to maintaining the status quo.

Scott Arciszewski
Chief Development Officer
Paragon Initiative Enterprises <https://paragonie.com>


Thread (25 messages)

« previous php.internals (#90460) next »