Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90252 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8891 invoked from network); 7 Jan 2016 15:20:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jan 2016 15:20:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=bishop.bettini@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=bishop.bettini@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.43 as permitted sender) X-PHP-List-Original-Sender: bishop.bettini@gmail.com X-Host-Fingerprint: 74.125.82.43 mail-wm0-f43.google.com Received: from [74.125.82.43] ([74.125.82.43:34296] helo=mail-wm0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 03/1F-21755-8528E865 for ; Thu, 07 Jan 2016 10:20:57 -0500 Received: by mail-wm0-f43.google.com with SMTP id u188so102595012wmu.1 for ; Thu, 07 Jan 2016 07:20:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=9CA/IwNPeKNZmAUZ/BAhJSu37XVmsPCMUsVGYYuvqnQ=; b=ANUPq0n9oA3UnCsnSII5ug1g5ezP9Gzgfu7lUfyPDtWrfD8qrZKm1kA6J/Dl8HszvZ YH5eQnCkciCVP5tShilOAjRknXRRboH5WxL8E1wLkl1w6Iw7PhSN4J1DJ0e5tVKgVUL/ FAE9BHLmq3/arxZ6mq3iTJLzXgy8DoF7mQjZyUxFm9SPE2VQqQFKdWW2X7aRyu2WMtRx jwPQIZSkq8gNL/CFG2agQEP0RLMsT2Vz2p73VB45isGLf2tPoiJIonu5j2BM5Nbf6zvx bcaXuVIPo4eBv93RefesYuFSnMtaOdKMrAjFLHIdjUt/alsiJI4igkEwqxobz+VWD4IL LLCA== X-Received: by 10.28.175.147 with SMTP id y141mr9833873wme.64.1452180053448; Thu, 07 Jan 2016 07:20:53 -0800 (PST) MIME-Version: 1.0 Reply-To: bishop@php.net Sender: bishop.bettini@gmail.com Received: by 10.194.45.230 with HTTP; Thu, 7 Jan 2016 07:20:24 -0800 (PST) In-Reply-To: References: Date: Thu, 7 Jan 2016 10:20:24 -0500 X-Google-Sender-Auth: sI4krMwTQbUb-tjbBsHaGuLfOzI Message-ID: To: Scott Arciszewski Cc: PHP Internals Content-Type: multipart/alternative; boundary=001a11443f0a3c5b950528c00487 Subject: Re: [PHP-DEV] [RFC] Libsodium From: bishop@php.net (Bishop Bettini) --001a11443f0a3c5b950528c00487 Content-Type: text/plain; charset=UTF-8 On Thu, Jan 7, 2016 at 8:26 AM, Scott Arciszewski wrote: > 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. > +1. Only comment is on namespace: how about \Php\Ext\Sodium? I don't know if namespacing PHP engine components has been standardized, but I feel we should limit how often the engine consumes names in the global namespace. E.g, I could see a user wanting "Sodium" for an app name, but couldn't use it simultaneously with the libsodium extension. --001a11443f0a3c5b950528c00487--