From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(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-14 03:40:49 |
Message-ID: | CAKt_ZftxFv5Gnd7j9hGuDqHos0bFx9eOAkrvAN=-zMOmRViZrw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Aug 13, 2016 at 9:37 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 8/13/2016 8:29 AM, support-tiger wrote:
>
>> experimented with this some more with no progress. only trust seems to
>> work which is not what we want - will try some more versions with md5 but
>> this is why I've called this out as such a pain point.
>>
>
> show us your pg_hba.conf (sans comments), and the connections that aren't
> working the way you want, along with whatever error messages they are
> generating.
It's worth noting how I normally set up this file:
1. Set up postgres user on local connections with peer authentication
2. Set up initial roles, passwords, etc. (sudo -u postgres psql, then
create role ... with noinherit login password = ...)
3. Configure for MD5 auth over the network and for all users on local
except postgres.
Of course that differs depending on environment and requirements but it is
a decent starting point.
>
>
>
>
> --
> john r pierce, recycling bits in santa cruz
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more
From | Date | Subject | |
---|---|---|---|
Next Message | Xtra Coder | 2016-08-14 07:28:30 | Re: Any reasons for 'DO' statement not returning result? |
Previous Message | John R Pierce | 2016-08-13 19:37:15 | Re: Postgres Pain Points: 1 pg_hba conf |