Re: [HACKERS] scram and \password - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] scram and \password
Date
Msg-id CAB7nPqRY_guD9cGBM7iMnfXw2eJY3gGLhd+0y-opJz8EVdjMHQ@mail.gmail.com
Whole thread Raw
In response to [HACKERS] scram and \password  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On Thu, Apr 6, 2017 at 8:04 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Thu, Apr 6, 2017 at 2:11 AM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>> At a quick glance, moving pg_frontend_random() to src/common looks like a
>> non-starter. It uses pglock_thread() which is internal to libpq, so it won't
>> compile as it is. I think I'm going to change scram_build_verifier() to take
>> a pre-generated salt as argument, to avoid the need for a random number
>> generator in src/common.
>
> Oops. Need an updated set of patches?

Attached is an updated set of patches anyway. This is similar to the
last set, except that I removed the part where pg_frontend_random() is
refactored, extending scram_build_verifier() to use a pre-generated
salt.

Hope that helps.
-- 
Michael

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Performance improvement for joins where outer side is unique
Next
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] Time to change pg_regress diffs to unified by default?