Re: use of the term "verifier" with SCRAM

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2019-10-12T19:48:37Z
Lists: pgsql-hackers
On 2019-10-10 10:03, Michael Paquier wrote:
> On Thu, Oct 10, 2019 at 09:08:37AM +0200, Peter Eisentraut wrote:
>> Here is my proposed patch to adjust this.
> 
> Looks fine to me reading through.  I think that you are right to not
> change the descriptions in build_server_final_message(), as that's
> described similarly in RFC 5802.

committed

> By renaming scram_build_verifier()
> to scram_build_secret() you are going to break one of my in-house
> extensions.  I am using it to register for a user SCRAM veri^D^D^D^D
> secrets with custom iteration and salt length :)

OK, that should be easy to work around with an #ifdef or two.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



Commits

  1. Fix use of term "verifier"