| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Christophe Courtois <christophe(dot)courtois(at)dalibo(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: pg_hba_file_rules: "scram-sha256" instead of "scram-sha-256" |
| Date: | 2018-01-30 22:07:20 |
| Message-ID: | c8037280-c3dd-9c8f-a565-fdf51a029e57@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 1/26/18 18:44, Michael Paquier wrote:
>> "scram-sha256" appears in commit c727f120 in src/backend/libpq/hba.c,
>> while defining the array UserAuthName.
>>
>> Is it just a remnant of previous versions of the patch or is there a
>> reason?
> Attached is a patch for that. At the same time I have noticed that
> protocol.sgml is using the same name, so I would suggest to fix that at
> the same time. That introduces a small user-visible change when using
> pg_hba_file_rules still that should be backpatched.
Committed and backpatched, and I also fixed the names of the internal
symbols analogously.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-01-30 22:56:44 | Re: pg_hba_file_rules: "scram-sha256" instead of "scram-sha-256" |
| Previous Message | Todd A. Cook | 2018-01-30 19:47:23 | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |