| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | meirav(dot)rath(at)imperva(dot)com, 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 02:29:02 |
| Message-ID: | 660079bb-b468-f41f-928e-1b3a46e17ae9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
This is not a bug - at least you haven't explained why the behavior
should be considered incorrect. This is a question and so belongs to
pgsql-general. Please, post it again to the right list.
On 01/29/2018 04:20 PM, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15035
> Logged by: Meirav Rath
> Email address: meirav(dot)rath(at)imperva(dot)com
> PostgreSQL version: 10.0
> Operating system: windows server 2012 R2
> Description:
>
> Hi,
>
> I'm trying to set up the new SCRAM-SHA-256 authentication method. The only
> problem is that the moment I set this in both postgresql.conf and
> pg_hba.conf I can no longer login with any user, and so I can't create new
> users with passwords that are compatible.
>
> Here's what pg_hba.conf looks like:
>
> ...
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Kohn | 2018-01-30 03:33:17 | Re: BUG #15036: Un-killable queries Hanging in BgWorkerShutdown |
| Previous Message | Tomas Vondra | 2018-01-30 02:17:12 | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |