Re: [PATCH] Refactoring: rename md5Salt to pwsalt

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Refactoring: rename md5Salt to pwsalt
Date: 2016-09-30 12:58:54
Message-ID: CAB7nPqQqQAR7N4w+KCyW+rsswfjfHN40SSJSFEL=n8Wt+hOBgw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 30, 2016 at 9:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> writes:
>> Suggested patch (first of many, I hope) renames `md5Salt` to more
>> general `pwsalt`.
>> Does it sound reasonable?
>
> I'm dubious. The main problem with supposing that port->md5Salt
> can serve other purposes is its fixed size. I think you're likely
> going to have to change that representation at some point (eg
> make it a separately-palloc'd field). My inclination would be to
> do the field renaming at the same time you change the representation,
> since that provides a convenient way to ensure you've caught every
> place that has to change.

SCRAM is going to use more than 4 bytes here. RFC5802 does not given
directly a length, the last set of patches has been using 10 bytes,
but at the end we are very likely to use more than that, and not 4 for
sure.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2016-09-30 13:08:44 Re: Tuplesort merge pre-reading
Previous Message Tom Lane 2016-09-30 12:40:56 Re: [PATCH] Refactoring: rename md5Salt to pwsalt