Restrict password hash length.
authorNathan Bossart <nathan@postgresql.org>
Mon, 7 Oct 2024 15:56:16 +0000 (10:56 -0500)
committerNathan Bossart <nathan@postgresql.org>
Mon, 7 Oct 2024 15:56:16 +0000 (10:56 -0500)
commit8275325a06ed91c053e046422a193dc6d56a70c5
treea93c19d78485bb1202206b6925f28e81f01f4496
parent022564f60ca5cade8fd663906f3ee514573b4b5e
Restrict password hash length.

Commit 6aa44060a3 removed pg_authid's TOAST table because the only
varlena column is rolpassword, which cannot be de-TOASTed during
authentication because we haven't selected a database yet and
cannot read pg_class.  Since that change, attempts to set password
hashes that require out-of-line storage will fail with a "row is
too big" error.  This error message might be confusing to users.

This commit places a limit on the length of password hashes so that
attempts to set long password hashes will fail with a more
user-friendly error.  The chosen limit of 512 bytes should be
sufficient to avoid "row is too big" errors independent of BLCKSZ,
but it should also be lenient enough for all reasonable use-cases
(or at least all the use-cases we could imagine).

Reviewed-by: Tom Lane, Jonathan Katz, Michael Paquier, Jacob Champion
Discussion: https://postgr.es/m/89e8649c-eb74-db25-7945-6d6b23992394%40gmail.com
src/backend/libpq/crypt.c
src/include/libpq/crypt.h
src/test/regress/expected/password.out
src/test/regress/sql/password.sql