postgres.git / summary / log / commit / refs

commit    d74a366aa2fa3f11fc4fbd1b2817ac252f6f9ba4
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Tue Nov 29 23:37:59 2022 +0000
First released in: 16.0, 11.19, 12.14, 13.10, 14.7, 15.2

    Fix comment in fe-auth-scram.c
    
    The frontend-side routine in charge of building a SCRAM verifier
    mentioned that the restrictions applying to SASLprep on the password
    with the encoding are described at the top of fe-auth-scram.c, but this
    information is in auth-scram.c.
    
    This is wrong since 8f8b9be, so backpatch all the way down as this is an
    important documentation bit.
    
    Spotted while reviewing a different patch.
    
    Backpatch-through: 11


 src/interfaces/libpq/fe-auth-scram.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/interfaces/libpq/fe-auth-scram.c b/src/interfaces/libpq/fe-auth-scram.c
index e71626580a7..c500bea9e74 100644
--- a/src/interfaces/libpq/fe-auth-scram.c
+++ b/src/interfaces/libpq/fe-auth-scram.c
@@ -892,7 +892,8 @@ pg_fe_scram_build_secret(const char *password, const char **errstr)
 	/*
 	 * Normalize the password with SASLprep.  If that doesn't work, because
 	 * the password isn't valid UTF-8 or contains prohibited characters, just
-	 * proceed with the original password.  (See comments at top of file.)
+	 * proceed with the original password.  (See comments at the top of
+	 * auth-scram.c.)
 	 */
 	rc = pg_saslprep(password, &prep_password);
 	if (rc == SASLPREP_OOM)


[parent: 8242752f9c10]