mirror of
https://github.com/postgres/postgres.git
synced 2025-07-18 17:42:25 +03:00
Minor cleanup/future-proofing for pg_saslprep().
Ensure that pg_saslprep() initializes its output argument to NULL in all failure paths, and then remove the redundant initialization that some (not all) of its callers did. This does not fix any live bug, but it reduces the odds of future bugs of omission. Also add a comment about why the existing failure-path coding is adequate. Back-patch so as to keep the function's API consistent across branches, again to forestall future bug introduction. Patch by me, reviewed by Michael Paquier Discussion: https://postgr.es/m/16558.1536407783@sss.pgh.pa.us
This commit is contained in:
@ -477,7 +477,7 @@ build_client_final_message(fe_scram_state *state)
|
||||
printfPQExpBuffer(&conn->errorMessage,
|
||||
"channel binding not supported by this build\n");
|
||||
return NULL;
|
||||
#endif /* HAVE_PGTLS_GET_PEER_CERTIFICATE_HASH */
|
||||
#endif /* HAVE_PGTLS_GET_PEER_CERTIFICATE_HASH */
|
||||
}
|
||||
#ifdef HAVE_PGTLS_GET_PEER_CERTIFICATE_HASH
|
||||
else if (conn->ssl_in_use)
|
||||
@ -747,7 +747,7 @@ verify_server_signature(fe_scram_state *state)
|
||||
char *
|
||||
pg_fe_scram_build_verifier(const char *password)
|
||||
{
|
||||
char *prep_password = NULL;
|
||||
char *prep_password;
|
||||
pg_saslprep_rc rc;
|
||||
char saltbuf[SCRAM_DEFAULT_SALT_LEN];
|
||||
char *result;
|
||||
|
Reference in New Issue
Block a user