Horton

Re: Password identifiers, protocol aging and SCRAM protocol

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: David Steele <david@pgmasters.net>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, Valery Popov <v.popov@postgrespro.ru>
Date: 2016-03-18T15:28:09Z
Lists: pgsql-hackers 
On Fri, Mar 18, 2016 at 9:31 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> That's not an issue for me to rebase this set of patches. The only
> conflicts that I anticipate are on 0009, but I don't have high hopes
> to get this portion integrating into core for 9.6, the rest of the
> patches is complicated enough, and everyone bandwidth is limited.

I really think we ought to consider pushing this whole thing out to
9.7.  I don't see how we're going to get all of this into 9.6, and
these are big, user-facing changes that I don't think we should rush
into under time pressure.  I think it'd be better to do this early in
the 9.7 cycle so that it has time to settle before the time crunch at
the end.  I predict this is going to have a lot of loose ends that are
going to take months to settle, and we don't have that time right now.
And I'd rather see all of the changes in one release than split them
across two releases.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Support SCRAM-SHA-256 authentication (RFC 5802 and 7677).

  2. Refactor SHA2 functions and move them to src/common/.

  3. Replace isMD5() with a more future-proof way to check if pw is encrypted.

  4. Remove bogus notice that older clients might not work with MD5 passwords.

  5. Refactor the code for verifying user's password.

  6. Replace PostmasterRandom() with a stronger source, second attempt.

  7. Remove support for (insecure) crypt authentication.