| commit | c20f2aab6ad4b41770fc8a066446c703bdf5d012 | |
| author | Tom Lane <tgl@sss.pgh.pa.us> | |
| Wed, 3 Jan 2024 22:40:38 +0000 (3 17:40 -0500) | ||
| committer | Tom Lane <tgl@sss.pgh.pa.us> | |
| Wed, 3 Jan 2024 22:40:38 +0000 (3 17:40 -0500) | ||
| tree | 5ea6d69ab38f02bfa2e52ad9cd93d360f96625f0 | treesnapshot (tar.gz zip) |
| parent | 54790f4b3f048db8f18e17966ad3bfb428e5b312 | commitdiff |
Avoid masking EOF (no-password-supplied) conditions in auth.c.
CheckPWChallengeAuth() would return STATUS_ERROR if the user does not
exist or has no password assigned, even if the client disconnected
without responding to the password challenge (as libpq often will,
for example). We should return STATUS_EOF in that case, and the
lower-level functions do, but this code level got it wrong since the
refactoring done in 7ac955b34. This breaks the intent of not logging
anything for EOF cases (cf. comments in auth_failed()) and might
also confuse users of ClientAuthentication_hook.
Per report from Liu Lang. Back-patch to all supported versions.
Discussion: https://postgr.es/m/b725238c-539d-cb09-2bff-b5e6cb2c069c@esgyn.cn
CheckPWChallengeAuth() would return STATUS_ERROR if the user does not
exist or has no password assigned, even if the client disconnected
without responding to the password challenge (as libpq often will,
for example). We should return STATUS_EOF in that case, and the
lower-level functions do, but this code level got it wrong since the
refactoring done in 7ac955b34. This breaks the intent of not logging
anything for EOF cases (cf. comments in auth_failed()) and might
also confuse users of ClientAuthentication_hook.
Per report from Liu Lang. Back-patch to all supported versions.
Discussion: https://postgr.es/m/b725238c-539d-cb09-2bff-b5e6cb2c069c@esgyn.cn
| src/backend/libpq/auth.c | diffblobblamehistory |