Thread: [COMMITTERS] pgsql: Rename "scram" to "scram-sha-256" in pg_hba.conf andpassword_en
[COMMITTERS] pgsql: Rename "scram" to "scram-sha-256" in pg_hba.conf andpassword_en
From
Heikki Linnakangas
Date:
Rename "scram" to "scram-sha-256" in pg_hba.conf and password_encryption. Per discussion, plain "scram" is confusing because we actually implement SCRAM-SHA-256 rather than the original SCRAM that uses SHA-1 as the hash algorithm. If we add support for SCRAM-SHA-512 or some other mechanism in the SCRAM family in the future, that would become even more confusing. Most of the internal files and functions still use just "scram" as a shorthand for SCRMA-SHA-256, but I did change PASSWORD_TYPE_SCRAM to PASSWORD_TYPE_SCRAM_SHA_256, as that could potentially be used by 3rd party extensions that hook into the password-check hook. Michael Paquier did this in an earlier version of the SCRAM patch set already, but I didn't include that in the version that was committed. Discussion: https://www.postgresql.org/message-id/fde71ff1-5858-90c8-99a9-1c2427e7bafb@iki.fi Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/c727f120ff50f624a1ee3abe700d995c18314a0b Modified Files -------------- doc/src/sgml/client-auth.sgml | 15 ++++++++------- doc/src/sgml/config.sgml | 4 ++-- src/backend/commands/user.c | 8 ++++---- src/backend/libpq/auth-scram.c | 2 +- src/backend/libpq/auth.c | 16 ++++++++-------- src/backend/libpq/crypt.c | 10 +++++----- src/backend/libpq/hba.c | 4 ++-- src/backend/libpq/pg_hba.conf.sample | 8 ++++---- src/backend/utils/misc/guc.c | 2 +- src/bin/initdb/initdb.c | 16 ++++++++-------- src/include/libpq/crypt.h | 2 +- src/test/authentication/t/001_password.pl | 14 +++++++------- src/test/authentication/t/002_saslprep.pl | 4 ++-- src/test/regress/expected/password.out | 8 ++++---- src/test/regress/sql/password.sql | 6 +++--- 15 files changed, 60 insertions(+), 59 deletions(-)