Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90470
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.42 as permitted sender)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAKws9z1g24rD=t92+9xKtO=3PuwQ3_N=L36gmVMqCC84CoqipQ@mail.gmail.com>
Date: Sun, 10 Jan 2016 18:56:57 -0500
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Message-ID: <1DDA7C76-5606-46DE-AF17-31E2FCC14018@heroku.com>
References: <CAKws9z1g24rD=t92+9xKtO=3PuwQ3_N=L36gmVMqCC84CoqipQ@mail.gmail.com>
To: Scott Arciszewski <scott@paragonie.com>
Subject: Re: [PHP-DEV] [RFC] Libsodium
From: dz@heroku.com (David Zuelke)

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
>