| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Meirav Rath <meirav(dot)rath(at)imperva(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15035: scram-sha-256 blocks all logins |
| Date: | 2018-01-30 14:04:17 |
| Message-ID: | CAKFQuwbgWAp2DuJ5N=ycFbfxO3aTn7Y4jvWpZFaUev=DHvL5KQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tuesday, January 30, 2018, Meirav Rath <meirav(dot)rath(at)imperva(dot)com> wrote:
> Yes, I was following a previous bug I found on your site -
> pg_hba_file_rules: "scram-sha256" instead of "scram-sha-256".
>
> So I fixed it, now pg_hba.conf looks like this:
>
> hostallall0.0.0.0/0scram-sha-256
> hostallpostgres0.0.0.0/0trust
>
From the docs:
Since the pg_hba.conf records are examined sequentially for each
connection attempt, the order of the records is significant. Typically,
earlier records will have tight connection match parameters and weaker
authentication methods, while later records will have looser match
parameters and stronger authentication methods.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Meirav Rath | 2018-01-30 14:15:00 | RE: BUG #15035: scram-sha-256 blocks all logins |
| Previous Message | PG Bug reporting form | 2018-01-30 10:15:59 | BUG #15037: gdal-libs-1.11.4-12 updates require proj unavailable version |