Re: [RFC][Vote] Libsodium vote closes; accepted (37-0)
| From: | David Zuelke | Date: | Tue, 14 Feb 2017 21:29:06 +0000 |
| Subject: | Re: [RFC][Vote] Libsodium vote closes; accepted (37-0) | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-98296@lists.php.net to get a copy of this message | ||
Will there be a renaming of the "libsodium" extension on PECL to "sodium" as
well, and will the two codebases be kept in sync?
Otherwise, libraries cannot, using Composer, express a dependency on "ext-sodium".
> On 10.02.2017, at 22:04, Scott Arciszewski <scott@paragonie.com> wrote:
>
> The vote for the Libsodium RFC has been closed. The final tally is 37 yes,
> 0 no.
>
> I'll begin working on the implementation with the desired API (sodium_*
> instead of \Sodium\*).
>
> Thank you for everyone who participated in these discussions over the past
> year or so and, of course, everyone who voted for better cryptography in
> PHP 7.2.
>
> Scott Arciszewski
> Chief Development Officer
> Paragon Initiative Enterprises <https://paragonie.com>