diff options
author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2016-12-12 12:48:13 +0200 |
---|---|---|
committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2016-12-12 12:48:13 +0200 |
commit | e7f051b8f9a6341f6d3bf80b29c1dbc1837be9ab (patch) | |
tree | 80671dc0282a774373dba495f6e29e7a7631d2ee /src/backend/tcop/postgres.c | |
parent | 58445c5c8d1424038d654ad9ee8af3724c60105e (diff) | |
download | postgresql-e7f051b8f9a6341f6d3bf80b29c1dbc1837be9ab.tar.gz postgresql-e7f051b8f9a6341f6d3bf80b29c1dbc1837be9ab.zip |
Refactor the code for verifying user's password.
Split md5_crypt_verify() into three functions:
* get_role_password() to fetch user's password from pg_authid, and check
its expiration.
* md5_crypt_verify() to check an MD5 authentication challenge
* plain_crypt_verify() to check a plaintext password.
get_role_password() will be needed as a separate function by the upcoming
SCRAM authentication patch set. Most of the remaining functionality in
md5_crypt_verify() was different for MD5 and plaintext authentication, so
split that for readability.
While we're at it, simplify the *_crypt_verify functions by using
stack-allocated buffers to hold the temporary MD5 hashes, instead of
pallocing.
Reviewed by Michael Paquier.
Discussion: https://www.postgresql.org/message-id/3029e460-d47c-710e-507e-d8ba759d7cbb@iki.fi
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions