Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86347 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46298 invoked from network); 22 May 2015 06:26:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 May 2015 06:26:51 -0000 Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 74.125.82.51 mail-wg0-f51.google.com Received: from [74.125.82.51] ([74.125.82.51:33157] helo=mail-wg0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/A3-14563-A2CCE555 for ; Fri, 22 May 2015 02:26:50 -0400 Received: by wgez8 with SMTP id z8so8075051wge.0 for ; Thu, 21 May 2015 23:26:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9I96VWR8xiAmz4HFEDXuqDnLAU/wtnbFcLhmfxE7VNI=; b=l1ONYNb+KlihliuztvZccAackaHSV806C4WBdnYppbQbn9gFNOOky5LSMvF+Mg1Ycm hjF02WpSko6Pz5FPKeAs+TSfBWM9ujNRhMGwQGhC2GH3rB1oIrqX4++qz/2AnSenD789 gjL8bQmulFZ/LqJQ2vIaIDHDutONeQgba94vlUMeQ9VDW8rnGaRzK0KDKf69rfm+gOS4 EWFNH0P9iUT/KHehanODjRHhuB9VJZ9T1wjGFTjLSJWLlf9AszKNf48P/5SZpdpyWGnM Q/3xAdqCWX5Fv/rwXDqVjrxEvO3j8pk+3BeVp7sUmvtFbRLL7V+JLgdqRMnas9UEem0g AR9A== X-Received: by 10.194.175.65 with SMTP id by1mr12396507wjc.152.1432276007907; Thu, 21 May 2015 23:26:47 -0700 (PDT) Received: from [192.168.2.120] (89-104-28-113.customer.bnet.at. [89.104.28.113]) by mx.google.com with ESMTPSA id l6sm6161970wib.18.2015.05.21.23.26.46 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 May 2015 23:26:46 -0700 (PDT) Sender: Michael Wallner Message-ID: <555ECC25.1040304@php.net> Date: Fri, 22 May 2015 08:26:45 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: Fwd: [PHP-DEV] [RFC] [PHP 7.1] libsodium From: mike@php.net (Michael Wallner) On 21/05/15 09:49, Peter Petermann wrote: > Hi Scott, > > I personally think the RFC is a bit short, > also I just had a very brief look at the documentation of the extension in > question, and find its API a bit strange, > whats up with having everything in static method calls? > > regards, > PP > > 2015-05-21 3:15 GMT+02:00 Scott Arciszewski : > >> The current state of cryptography in PHP is, well, abysmal. Our two main >> choices for handling symmetric cryptography are libmcrypt (collecting dust >> since 2007) and openssl, which lacks a streaming API (e.g. mcrypt_generic) >> and GCM support. >> >> >> I think now is a good time to talk about the possibility of making >> libsodium a core PHP extension, depending on where things are when we near >> the 7.1 feature freeze. >> >> I've just opened an RFC for precisely this purpose: >> https://wiki.php.net/rfc/libsodium >> Yes, the choice of API looks pretty awkward; if we could settle on PHP-5.6+, change Sodium to a namespace and all methods to functions therein. -- Regards, Mike