Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107910 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 38605 invoked from network); 12 Dec 2019 11:12:56 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 12 Dec 2019 11:12:56 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 5AB2C2C1252 for ; Thu, 12 Dec 2019 01:11:31 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: X-Spam-Virus: No Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Thu, 12 Dec 2019 01:11:30 -0800 (PST) Received: by mail-lj1-x234.google.com with SMTP id a13so1395590ljm.10 for ; Thu, 12 Dec 2019 01:11:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ap6VmgOIElvrIfhEt92RbuaEtKgdhTyviovATSjr94M=; b=CAoSCVCCH51BNNNAsXOzLUNTKBaxLpFPxBN0RbnL3HX9qoTkFYr7zQNEEDSHVUT9jx DAQOnOExfpV1mTt/D5mrmz8NvwDdI7a2jIUdeWf7Q/sU5r5magHoEquOc+6cx5SbVFFM xGHL3IFb+zdVbgZWiTwVmPuXKVLh8EDLm2tPXSrRlnFfieGIdwR5/Qs7oPQOhuyKtZty wubnlikuruH8IstIa27TFZzsmpwemmNCKY1OtvntvD7ZJIkmWglefVCVHIkvULqzEg75 nucN0E5y1Gm7l3w4f4gS+DhYAQmMavmcC4s0yLtVwUTFMV/6YH79EeOAZvyUDafHkEdL lNsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ap6VmgOIElvrIfhEt92RbuaEtKgdhTyviovATSjr94M=; b=uCslpBVJBkrLXr8xM1I3tKSB2yj6ow15Pt1SQmAh7ZJPHlj77YiNiII+IBXcX8SWO1 Bffj+OHof+nozhd2NFTPyy25bMZvMLO6MSHuQvWyO9/nSRLCWE/mhMMhM1gV5ya5mneH +3BNGZ7f362A6a3+pySZ+EzidxSESOBXo+N7ODvDtDmvTM33zsKitib2zHycwV8r0TOm fb5636ZNtsak4vIfOKHirSjjhTN7CtyjeC+h45dMnbXW3ZZ1x7R5p+UHnZuyATLHdQY0 HcVmdoYXH6ofnkg3vC1YHzep/v6wcB8Tw/7Pw3KZTg3uodhVkjCQXKQqzqgSS/WjKRHw tqJQ== X-Gm-Message-State: APjAAAXosaZlvx+1fAB+A1LcB2n/+9sgXN/OT7AVyOLg32hua6ckRznD kNogLDieOicR+r+tu2gAu46CKbDlqK+7d3uMkeYySXG7+sO0ag== X-Google-Smtp-Source: APXvYqzZgdrjz0Ke6wCDXPOwdoAVM3QHoLiCNxbpvnwvZOxlTGd1T4pUpz2LA3IqdTN3cs/06HA/QMa1i4aAmJOTpLg= X-Received: by 2002:a2e:96da:: with SMTP id d26mr5005966ljj.6.1576141888983; Thu, 12 Dec 2019 01:11:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 12 Dec 2019 10:11:13 +0100 Message-ID: To: Sara Golemon Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000068957c05997e2170" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC][Accepted] Password Mechanism Registry From: nikita.ppv@gmail.com (Nikita Popov) --00000000000068957c05997e2170 Content-Type: text/plain; charset="UTF-8" On Tue, Nov 20, 2018 at 8:05 PM Sara Golemon wrote: > https://wiki.php.net/rfc/password_registry has been accepted > unanimously 21:0 with the supplemental vote on maintaining BC for the > integer based mechanism parameters passing 19:1. > > Implementation will be forthcoming. > > -Sara > Hey Sara, After seeing https://stackoverflow.com/questions/59273258/identifying-what-password-default-will-be-in-php-7-4, I'm wondering what the rationale is for making PASSWORD_DEFAULT null, rather than giving it the value of whatever PASSWORD_* is the default? Checking PASSWORD_DEFAULT == PASSWORD_BCRYPT doesn't seem like an unreasonable thing to do... Nikita --00000000000068957c05997e2170--