Re: Postgres Pain Points: 1 pg_hba conf - Mailing list pgsql-general

From Francisco Olarte
Subject Re: Postgres Pain Points: 1 pg_hba conf
Date
Msg-id CA+bJJbwbO3X4YrhU8_FRiNqgZTOg7hY0mNqSPmva1Z2Oqv02BA@mail.gmail.com
Whole thread Raw
In response to Postgres Pain Points: 1 pg_hba conf  (support-tiger <support@tigernassau.com>)
List pgsql-general
On Thu, Aug 11, 2016 at 7:04 PM, support-tiger <support@tigernassau.com> wrote:
....
> #1) pg_hba conf
> Out of the box the md5 setting blocks access. Most "advice" say change to
> "all all trust" and indeed that works.  But that seems a big security issue.

Indeed it is. I do not know where do you get this "advice" from, but
I'll seriously consider blackholing the source.

> Specifying a postgres role, password, and peer does not seem to work.  And
> this approach is problematic if there are many roles or even dynamically
> created roles.

In general this works, in nearly every situation.  If you have
problems, consider explaining it and may be you wil get some
``advice''.

Francisco Olarte.


pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Postgres Pain Points 2 ruby / node language drivers
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Postgres Pain Points 2 ruby / node language drivers