]> granicus.if.org Git - postgresql/commit
Rename "scram" to "scram-sha-256" in pg_hba.conf and password_encryption.
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>
Tue, 18 Apr 2017 11:50:50 +0000 (14:50 +0300)
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>
Tue, 18 Apr 2017 11:50:50 +0000 (14:50 +0300)
commitc727f120ff50f624a1ee3abe700d995c18314a0b
treea3fb2b94b43e51f386d31dca2b056d004b787ae3
parent123aaffb5b881f3dadaac676877a90b50233a847
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
15 files changed:
doc/src/sgml/client-auth.sgml
doc/src/sgml/config.sgml
src/backend/commands/user.c
src/backend/libpq/auth-scram.c
src/backend/libpq/auth.c
src/backend/libpq/crypt.c
src/backend/libpq/hba.c
src/backend/libpq/pg_hba.conf.sample
src/backend/utils/misc/guc.c
src/bin/initdb/initdb.c
src/include/libpq/crypt.h
src/test/authentication/t/001_password.pl
src/test/authentication/t/002_saslprep.pl
src/test/regress/expected/password.out
src/test/regress/sql/password.sql