On 8/16/2016 1:32 PM, support-tiger wrote:
localall all trust
so all unix 'domain' connections will allow any process on the system to
authenticate as any SQL user.I nearly always use peer here. my
applications which want to connect as a different
On 08/13/2016 01:37 PM, John R Pierce 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
On Sat, Aug 13, 2016 at 9:37 PM, John R Pierce 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
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 c
On 8/11/2016 1:48 PM, Jeff Janes wrote:
#1) pg_hba conf
>Out of the box the md5 setting blocks access.
That depends on which box you got it out of. If you compile the
source yourself, its default settings are 'trust', not 'md5'.
If you get it from a repository, it is up to the repository's pol
On Thu, Aug 11, 2016 at 10:04 AM, support-tiger wrote:
> We have always been impressed with the Postgres project and team. The whole
> hybrid SQL / JSONB functionality rocks. The scalability rocks. The speed
> and stability rock. At the command line, Postgres rocks. But in
> applications we ha
On Thu, Aug 11, 2016 at 11:04:37AM -0600, support-tiger 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.
> Specifying a postgres role, password, and peer does not seem
On Thu, Aug 11, 2016 at 7:04 PM, support-tiger 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,
On 08/11/2016 10:04 AM, support-tiger wrote:
We have always been impressed with the Postgres project and team. The
whole hybrid SQL / JSONB functionality rocks. The scalability rocks.
The speed and stability rock. At the command line, Postgres rocks. But
in applications we have had some real,
We have always been impressed with the Postgres project and team. The
whole hybrid SQL / JSONB functionality rocks. The scalability rocks.
The speed and stability rock. At the command line, Postgres rocks. But
in applications we have had some real, and not improving pain points:
#1) pg_hba
10 matches
Mail list logo
