Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97807
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain paragonie.com designates 209.85.218.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMUwpuTeJfaaCMMU4cDvwXRoHjZaVwNkZMg5KA1VOjm5zJq0Gw@mail.gmail.com>
References: <CAKws9z2x1wz_WA9_XWOjbf-M9m917DN=zWzhXw3JNqdewyL_9g@mail.gmail.com>
 <CAMUwpuTeJfaaCMMU4cDvwXRoHjZaVwNkZMg5KA1VOjm5zJq0Gw@mail.gmail.com>
Date: Tue, 17 Jan 2017 05:49:27 -0500
Message-ID: <CAKws9z3Es5TP0A-COpFnpW2+7Fe2csi-3FvgC59s9_1JnG4FXg@mail.gmail.com>
To: Julien Pauli <jpauli@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113ce83ce0e62f0546480d0d
Subject: Re: [PHP-DEV] [RFC] libsodium (PHP 7.2)
From: scott@paragonie.com (Scott Arciszewski)

--001a113ce83ce0e62f0546480d0d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 12, 2017 at 5:23 AM, Julien Pauli <jpauli@php.net> wrote:

> On Wed, Jan 11, 2017 at 7:22 PM, Scott Arciszewski <scott@paragonie.com>
> wrote:
>
>> Hi all,
>>
>> I'm resurrecting my RFC to add libsodium as a core extension to PHP 7.2.
>>
>> In response to feedback from Pierre Joye, I've outlined which parts of t=
he
>> existing libsodium API I'd like exposed in the core extension. Most
>> notably:
>>
>> - Removed crypto_aead_aes256gcm_* because OpenSSL offers it
>> - Removed crypto_aead_chacha20poly1305_* because crypto_aead_* is awaiti=
ng
>> the CAESAR winner https://competitions.cr.yp.to/caesar.html
>> - Removed crypto_pwhash_scryptsalsa208sha256_* because we have Argon2i
>> now
>>
>> If anyone would like to weigh in on this in the next few weeks, I'd
>> greatly
>> appreciate it.
>>
>> I'm also developing a polyfill for most of the API features (except
>> pwhash): https://github.com/paragonie/sodium_compat
>>
>>
> I guess you are talking about this : https://wiki.php.net/rfc/libsodium
>
> Huge +1.
>
> =E2=80=8B=E2=80=8B
>
> What about libsodium usage under Windows ?
> I guess under *Nix, we'll rely on the OS shipping of the library , but
> that's not the same flavour for Windows, where we usually need to embed,
> and maintain the library.
>
> I see a second vote for the API , PHP is not really a language where
> You\Use\Things\Like\That , I'm all +1 to use_things_like_that() instead :=
-)
>
> After Mcrypt has been abandonned , we really really need such a library
> binding added to Core IMO.
>
>
> Julien.Pauli
>

=E2=80=8BYep, that's the correct URL.=E2=80=8B
=E2=80=8B

> What about libsodium usage under Windows ?
> I guess under *Nix, we'll rely on the OS shipping of the library , but
> that's not the same flavour for Windows, where we usually need to embed,
> and maintain the library.

=E2=80=8B
=E2=80=8BI'll defer to Pierre Joye on the =E2=80=8Bintricacies involved wit=
h Windows, as
that's a topic I'm mostly unfamiliar with. Sorry I can't offer much more in
response to that.

Scott Arciszewski
Chief Development Officer
Paragon Initiative Enterprises <https://paragonie.com/>=E2=80=8B

--001a113ce83ce0e62f0546480d0d--