Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90474 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73155 invoked from network); 11 Jan 2016 06:57:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jan 2016 06:57:19 -0000 Authentication-Results: pb1.pair.com header.from=scott@paragonie.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=scott@paragonie.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain paragonie.com from 209.85.217.176 cause and error) X-PHP-List-Original-Sender: scott@paragonie.com X-Host-Fingerprint: 209.85.217.176 mail-lb0-f176.google.com Received: from [209.85.217.176] ([209.85.217.176:36088] helo=mail-lb0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4F/A0-64385-E4253965 for ; Mon, 11 Jan 2016 01:57:18 -0500 Received: by mail-lb0-f176.google.com with SMTP id oh2so249331602lbb.3 for ; Sun, 10 Jan 2016 22:57:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paragonie-com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:content-type; bh=VKjG5KAcVjssSRzY+VWy+MMbCNZiKmf7yALJ+0m+0OA=; b=K36LiKuh6PChKMBJeuZpUYo3JNua0HAFZV72Ww3b9SVYqiMINz0JkW9NijOvxwsi92 +BIEqfLKWxIZQfQktd8Y8/V9p9cPtrScB3lnXHc3Hm1selWFf+YJDf5PK+S1MVYmaEak YBfDBIqs/7yaoVOE8kd4mpHd4k4DDbsxmlDb48y7oWWJw/nQh4u6YMcprDebIZ4UGsl8 qfv2wQQ8euKLZDXkPLRGLVh4WSVfmfWnQ5Aow+TOPekK8MLBt9gUs3qReB8PslfgLrk1 ZJkevharyj1hiwV7254XX00uYZWdi/duvORKxZHuhYRCUMBmAdu2Z81CUuP+iKxwdQoN UPNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=VKjG5KAcVjssSRzY+VWy+MMbCNZiKmf7yALJ+0m+0OA=; b=Sms9BQE9DHeJSkTFvd5mjvkgdGepvKPhbdSca3GBtItwUB7HPYmjDBFEDwhFLhIPQb w6pVpoeEUvTKZFB+eTC+q+RxV6RmKu78MGjlFZrtZ9tIGKO8eFy4x+aPO3koMyQrhPKL XYRKH1vnhsp75WuIs7iR5hCj6u31hMu9EmrwLSjNHlMMODCTN7/DHP506voXSinmWmJo 1RmSY5tyk5YoFwlGgvjJcZ56xmNmFl/wOAwdIygfQuuvXsiBz452rA9DMW3vTDtPCWw1 oC5Fc2PNtKGJBp/2Yr8pefIq6sKXHFQlJFFD3XCkwu82IbJTxPFDd3pAXmsM0ITktKqR YR7g== X-Gm-Message-State: ALoCoQnLABESE1i0xA4V8sEMSI8iBe217mC+ITiKU5Mx+U8x53BGj5t7qSZFniNhnQxVCrXv4A+SmfOoiuQoY2ZsFeLmuGQbgQ== MIME-Version: 1.0 X-Received: by 10.112.181.196 with SMTP id dy4mr28806639lbc.42.1452495435525; Sun, 10 Jan 2016 22:57:15 -0800 (PST) Received: by 10.114.160.13 with HTTP; Sun, 10 Jan 2016 22:57:15 -0800 (PST) Date: Mon, 11 Jan 2016 01:57:15 -0500 Message-ID: To: PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: PHP 7.1 - Argon2 From: scott@paragonie.com (Scott Arciszewski) Does adding Argon2 as a possible choice for password_hash() + password_verify() need an RFC? Or can I just submit a pull request? It won't be changing the default in 7.1, and IIRC this sort of change was already agreed upon as part of the original password_hash() RFC. Scott Arciszewski Chief Development Officer Paragon Initiative Enterprises