Re: hostnossl in pg_hba.conf demands a password

From: Venkata B Nagothi <nag1010(at)gmail(dot)com>
To: John Scalia <jayknowsunix(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: hostnossl in pg_hba.conf demands a password
Date: 2016-11-14 21:20:42
Message-ID: CAEyp7J_Y5sG0MSUyPCFPencprUAVeHEbfH=sv6vpwxtzgkEumQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Nov 15, 2016 at 8:10 AM, John Scalia <jayknowsunix(at)gmail(dot)com> wrote:

> I've been experimenting a bit with both 9.4.10 and 9.6.0 and both of these
> are exhibiting the same behavior. I've been setting up zabbix and the local
> agent requires a trust connection. So, if my pg_hba.conf has a line:
>
> host all monitoring. 127.0.0.1/32.
> trust
>
> It works as I expected, but if I change "host" to "hostnossl" and reload,
> it then demands a password for the monitoring user.
>
> The servers are configured with SSL and all other connections require
> "hostssl", but the zabbix agent is not configured with SSL. I'd say this
> behavior is a bug, but maybe I missed reading the fine manual somewhere.
> Has anyone else seen this or maybe the docs need updating.

Do you have any other entries (for 127.0.0.1) in pg_hba.conf which is
generating this behaviour ?

Regards,

Venkata B N
Database Consultant

Fujitsu Australia

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message John Scalia 2016-11-14 21:23:05 Re: hostnossl in pg_hba.conf demands a password
Previous Message John Scalia 2016-11-14 21:10:14 hostnossl in pg_hba.conf demands a password