On Sat, Apr 22, 2017 at 7:20 AM, Michael Paquier <michael.paqu...@gmail.com> wrote: > Do we really want to add a new function or have a hard failure? Any > application calling PQencryptPassword may trap itself silently if the > server uses scram as hba key or if the default is switched to that, > from this point of view extending the function makes sense as well.
Attached is a new patch set, taking into account the new format. -- Michael
0001-Move-routine-to-build-SCRAM-verifier-into-src-common.patch
Description: Binary data
0002-Refactor-frontend-side-random-number-generation.patch
Description: Binary data
0003-Extend-PQencryptPassword-with-a-hashing-method.patch
Description: Binary data
0004-Extend-psql-s-password-and-createuser-to-handle-SCRA.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers