[pgpool-general: 3136] Re: why using MD5 auth on the backends requires using pool_hba.conf?
Tatsuo Ishii
ishii at postgresql.org
Wed Sep 3 00:28:41 JST 2014
Good point.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
> I would imagine it is to keep the security model of pgpool in line with the security model of postgresql. Specifically, so you can limit what database and account combinations are accessible from which locations, as the postgresql hba file is rendered (more or less) useless as all connections to postgresql come from your pgpool box(es).
>
> On 08/31/2014 03:58 AM, Kent Tong wrote:
>> Hi,
>>
>> I understand that using MD5 auth on the backends requires pool_passwd,
>> but why does it also requires using pool_hba.conf?
>>
>> thanks!
>>
>> --
>> Kent Tong
>> IT author and consultant, child education coach
>>
>>
>> _______________________________________________
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>>
>
> --
> Ryan DeShone
>
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
More information about the pgpool-general
mailing list