Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93816
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.154 cause and error)
To: Scott Arciszewski <scott@paragonie.com>
References: <CAKws9z114YcHkDaXO3o-E0JuHR10WsPzyedeF_8Q=shHDziwug@mail.gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Message-ID: <341f7e46-daa3-de94-fb0a-fdff999a08b0@telia.com>
Date: Sun, 5 Jun 2016 15:09:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CAKws9z114YcHkDaXO3o-E0JuHR10WsPzyedeF_8Q=shHDziwug@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Libsodium - Discussion
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)

Hi,
Den 2016-06-01 kl. 09:49, skrev Scott Arciszewski:
> Hi PHP Internals Team,
>
> Let's begin discussing the prospect of adding libsodium as a core extension
> in PHP 7.1. I've updated the RFC to explain why this would be a good idea
> and the benefits it offers.
>
> https://wiki.php.net/rfc/libsodium
>
> If the subsequent discussion goes smoothly, I would like to open voting on
> June 15.
>
> Together, let's make PHP cryptography so safe that it becomes boring.
>
> Scott Arciszewski
> Chief Development Officer
> Paragon Initiative Enterprises <https://paragonie.com>
>
Given the lively discussion I suggest that the RFC has an "Discussion Point"
subject where the "Current postion" is clarified for important topics, 
like in
https://wiki.php.net/rfc/scalar_type_hints_v5 RFC. I think it would help in
moving things forward.

I also wonder what is the minimum amount of changes needed for making
libsodium fly and what is unrealistic (needs to be handled outside 
libsodium)
even if we talk about 7.x perspective?

Regards //Björn Larsson