Re: [RFC] Libsodium
| From: | David Zuelke | Date: | Sun, 10 Jan 2016 23:56:57 +0000 |
| Subject: | Re: [RFC] Libsodium | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-90470@lists.php.net to get a copy of this message | ||
Can we call that extension "sodium" please without the "lib" prefix?
David
> On 07.01.2016, at 08:26, Scott Arciszewski <scott@paragonie.com> wrote:
>
> Hi everyone,
>
> I've updated the RFC to make libsodium a core PHP extension in 7.1, to
> include references to the online documentation.
>
> https://wiki.php.net/rfc/libsodium
>
> All new functions and classes would exist in the Sodium namespace. e.g.
>
> $ciphertext = \Sodium\crypto_box($message, $nonce, $keypair);
>
> This is part of an overall effort to improve PHP's cryptography; up
> next will be the pluggable crypto API that supports multiple backends
> (with a scope limited to openssl and libsodium at the time of release)
> but always provide conservative defaults. Then I'd like to look at
> deprecating ext/mcrypt back to PECL and add more hash functions to
> ext/hash.
>
> Scott Arciszewski
> Chief Development Officer
> Paragon Initiative Enterprises <https://paragonie.com>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>