Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103426
Return-Path: <php@golemon.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 84196 invoked from network); 6 Nov 2018 20:40:32 -0000
Received: from unknown (HELO mail-qt1-f170.google.com) (209.85.160.170)
  by pb1.pair.com with SMTP; 6 Nov 2018 20:40:32 -0000
Received: by mail-qt1-f170.google.com with SMTP id l9-v6so3399330qtj.12
        for <internals@lists.php.net>; Tue, 06 Nov 2018 08:58:57 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=HrokKDcppp0xAD4On3YJoxdL88Pf7hn3koyRglvmHQk=;
        b=e4KGUQISfyJgf6RaHZqX2LD0WlRBE6FzYDtLfS1PtqX5XKJPXOHzZsKlhlv5YwEAEt
         yixZhsqoO4tujc11pKgTi+axoLzs4Zepf26hWrkW9zfaXrzvKdwgMRRe8tcRtQHrdQQI
         sUUvHwK0PeGjzylIdJBG2iM2QZKP86T8gVlSXbaf9u45sCG2pUkWuX8z437eW3sc3iyV
         oO8U4M6081VqzWVJBHUq52JLo8vbYe2tsp2U+WQy33Cez6xjl7/FxkkgXdTEiAmEzXzp
         pqS+tlBsEWagOkoID3s9dTcSX22mww6XwBX+uhMKGgUzmmI+UpuiYYDYoCy5j/rIhgMt
         Nzaw==
X-Gm-Message-State: AGRZ1gLziQYl8LfiuKcYqFdZoUh9TfbpUjbS5B6ovCzLU8bb4CnWvWHe
	I7rJLRatiIvKJB61wlre2PrjMXkYpS790/XzIm8amjSAk2w=
X-Google-Smtp-Source: AJdET5ffWdrTLPqGikt2yCiXrSaOaVuprXCP513odXBYXEuBGtVv9t8G7JGg3isz7ym5cXoihHIM7vZLthXojn/Xhvc=
X-Received: by 2002:ac8:548a:: with SMTP id h10mr24124794qtq.15.1541523537261;
 Tue, 06 Nov 2018 08:58:57 -0800 (PST)
MIME-Version: 1.0
Date: Tue, 6 Nov 2018 10:58:46 -0600
Message-ID: <CAESVnVrkOSN=9n+3rhTM=9SxnDNB4Vov2MOjE5RPcJoLb8Ukxw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: [RFC][VOTE] Password Digest Mechanism Registry
From: pollita@php.net (Sara Golemon)

There's been no further discussion about password digest registry
after the initial post on 15 Oct despite a reminder post a week later,
so I'm going to go ahead and move the RFC into voting.
https://wiki.php.net/rfc/password_registry

Reminder that this RFC is mostly non user facing, it just provides
mechanisms for extensions to register hashing handlers for the
password_*() functions.  The primary user-facing effect of this is
that password scheme identifiers have changed.  There is a secondary
question on the RFC to address the BC impact of this.

-Sara