| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Meirav Rath <meirav(dot)rath(at)imperva(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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>, PG Bug reporting form <noreply(at)postgresql(dot)org> |
| Subject: | Re: BUG #15035: scram-sha-256 blocks all logins |
| Date: | 2018-01-30 08:10:18 |
| Message-ID: | 20180130081018.GA21433@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jan 30, 2018 at 07:56:40AM +0000, Meirav Rath wrote:
> <snip>
> host all all 0.0.0.0/0 scram-sha256
> <snip>
>
> Because I can’t restart the postgresql service, it crashes when this
> is the setup. User postgres is the superuser, by the way.
You need to make the difference between a crash and what seems to just
be an incorrect configuration which prevents your server to start. If
you look at the line above which I have taken from the pg_hba.conf you
have written in your last email, it is incorrect. "scram-sha256" is not
a correct HBA method. You need to use "scram-sha-256" instead.
I would advise to look at the documentation correctly first:
https://www.postgresql.org/docs/devel/static/auth-pg-hba-conf.html
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Meirav Rath | 2018-01-30 08:28:19 | RE: BUG #15035: scram-sha-256 blocks all logins |
| Previous Message | Daniel Gustafsson | 2018-01-30 08:02:47 | Re: BUG #15035: scram-sha-256 blocks all logins |