Re: Raising the SCRAM iteration count

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>
To: Michael Paquier <michael@paquier.xyz>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-03-07T13:03:05Z
Lists: pgsql-hackers

Attachments

> On 7 Mar 2023, at 09:26, Daniel Gustafsson <daniel@yesql.se> wrote:

> Right, what I meant was: can a pg_regress sql/expected test drive a psql
> interactive prompt?  Your comments suggested using password.sql so I was
> curious if I was missing a neat trick for doing this.

The attached v7 adds a TAP test for verifying that \password use the changed
SCRAM iteration count setting, and dials back the other added test to use fewer
iterations than the default setting in order to shave (barely noticeable
amounts of) cpu cycles.

Running interactive tests against psql adds a fair bit of complexity and isn't
all that pleasing on the eye, but it can be cleaned up and refactored when
https://commitfest.postgresql.org/42/4228/ is committed.

--
Daniel Gustafsson

Commits

  1. Test SCRAM iteration changes with psql \password

  2. Make SCRAM iteration count configurable