| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | support-tiger <support(at)tigernassau(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres Pain Points: 1 pg_hba conf |
| Date: | 2016-08-11 17:44:01 |
| Message-ID: | CA+bJJbwbO3X4YrhU8_FRiNqgZTOg7hY0mNqSPmva1Z2Oqv02BA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Aug 11, 2016 at 7:04 PM, support-tiger <support(at)tigernassau(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2016-08-11 18:02:06 | Re: Postgres Pain Points 2 ruby / node language drivers |
| Previous Message | David G. Johnston | 2016-08-11 17:43:03 | Re: Postgres Pain Points 2 ruby / node language drivers |