From b4675a8ae2d0aaafeb136c46c92bb56eaf018d32 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Sat, 12 Oct 2019 21:17:34 +0200 Subject: Fix use of term "verifier" Within the context of SCRAM, "verifier" has a specific meaning in the protocol, per RFCs. The existing code used "verifier" differently, to mean whatever is or would be stored in pg_auth.rolpassword. Fix this by using the term "secret" for this, following RFC 5803. Reviewed-by: Michael Paquier Discussion: https://www.postgresql.org/message-id/flat/be397b06-6e4b-ba71-c7fb-54cae84a7e18%402ndquadrant.com --- src/interfaces/libpq/fe-auth-scram.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/interfaces/libpq/fe-auth-scram.c') diff --git a/src/interfaces/libpq/fe-auth-scram.c b/src/interfaces/libpq/fe-auth-scram.c index 693739c5442..741f566a724 100644 --- a/src/interfaces/libpq/fe-auth-scram.c +++ b/src/interfaces/libpq/fe-auth-scram.c @@ -822,10 +822,10 @@ verify_server_signature(fe_scram_state *state) } /* - * Build a new SCRAM verifier. + * Build a new SCRAM secret. */ char * -pg_fe_scram_build_verifier(const char *password) +pg_fe_scram_build_secret(const char *password) { char *prep_password; pg_saslprep_rc rc; @@ -851,7 +851,7 @@ pg_fe_scram_build_verifier(const char *password) return NULL; } - result = scram_build_verifier(saltbuf, SCRAM_DEFAULT_SALT_LEN, + result = scram_build_secret(saltbuf, SCRAM_DEFAULT_SALT_LEN, SCRAM_DEFAULT_ITERATIONS, password); if (prep_password) -- cgit v1.2.3