Re: Improve error handling of HMAC computations and SCRAM
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Sergey Shinderuk <s.shinderuk@postgrespro.ru>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-01-12T03:56:17Z
Lists: pgsql-hackers
On Tue, Jan 11, 2022 at 11:08:59AM +0300, Sergey Shinderuk wrote: > Yeah, that's better. I thought "providing errors about an error" was a > typo, but now I see the same comment was committed in b69aba745. Is it just > me? :) It is not only you :) I have applied a fix to fix the comments on HEAD and REL_14_STABLE. Attached is a rebased patch for the HMAC portions, with a couple of fixes I noticed while going through this stuff again (mostly around SASLprep and pg_fe_scram_build_secret), and a fix for a conflict coming from 9cb5518. psql's \password is wrong to assume that the only error that can happen for scran-sha-256 is an OOM, but we'll get there. -- Michael
Commits
-
Improve error handling of HMAC computations
- 5513dc6a304d 15.0 landed
-
Fix incorrect comments in hmac.c and hmac_openssl.c
- 3c1ffd02dd05 14.2 landed
- 87f29f4fcc4e 15.0 landed
-
Fix comment related to pg_cryptohash_error()
- af8d530e4758 14.2 landed
- 9a3d8e188667 15.0 landed