Re: Password identifiers, protocol aging and SCRAM protocol

Valery Popov <v.popov@postgrespro.ru>

From: Valery Popov <v.popov@postgrespro.ru>

To: Michael Paquier <michael.paquier@gmail.com>

Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, david@pgmasters.net

Date: 2016-03-16T12:14:23Z

Lists: pgsql-hackers

Hi!

On 03/15/2016 06:59 PM, Michael Paquier wrote:
> The set of patches I am proposing here does not go through those code 
> paths, and this is likely an aggregate failure. 
Michael, you were right. It was incorrect installation of contrib binaries.
Now all tests pass OK, both check-world and installcheck-world,
Thanks.

-- 
Regards,
Valery Popov
Postgres Professional http://www.postgrespro.com
The Russian Postgres Company

Commits

Support SCRAM-SHA-256 authentication (RFC 5802 and 7677).
- 818fd4a67d61 10.0 landed
Refactor SHA2 functions and move them to src/common/.
- 273c458a2b3a 10.0 landed
Replace isMD5() with a more future-proof way to check if pw is encrypted.
- dbd69118c05d 10.0 landed
Remove bogus notice that older clients might not work with MD5 passwords.
- 7e3ae5455948 9.2.20 landed
- 470af1f41c8b 9.3.16 landed
- ada2cdb61015 9.4.11 landed
- 65a7f190b253 9.5.6 landed
- 7546c135dc30 9.6.2 landed
- 31c54096a18f 10.0 landed
Refactor the code for verifying user's password.
- e7f051b8f9a6 10.0 landed
Replace PostmasterRandom() with a stronger source, second attempt.
- fe0a0b5993df 10.0 landed
Remove support for (insecure) crypt authentication.
- 53a5026b5cb3 8.4.0 cited