Re: proper pg_hba config to require ssl from non-local/private ips - Mailing list pgsql-admin

From Matthew Lenz
Subject Re: proper pg_hba config to require ssl from non-local/private ips
Date
Msg-id CANpBAJvYy8LNPpWZwThNNcLg++Hoz5QooB0w9MqZmicwK9U+rg@mail.gmail.com
Whole thread Raw
In response to Re: proper pg_hba config to require ssl from non-local/private ips  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin
They are external internet routable ips.  They will not match any of the host lines.

On Wed, Oct 19, 2022 at 10:00 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Wed, 2022-10-19 at 07:49 -0500, Matthew Lenz wrote:
> This is what I've got currently but it's still allowing non-ssl connections from remote (non-local/private) hosts. Any thoughts?
>
> local   all             all                                     trust
> host    all             all             127.0.0.1/32            trust
> host    all             all             ::1/128                 trust
> host    all             all             10.0.0.0/8              md5
> host    all             all             172.16.0.0/12           md5
> hostssl all             all             all                     md5 clientcert=verify-ca
>
> Also when I require SSL on the client it allows SSL connections without a CA signed cert
> which I thought clientcert=verify-ca in this pg_hba should require.

Then your client IP address must match the CIDR 172.16.0.0/12, right?

That line matches both unencrypted and encrypted connections, that's why it is used
for SSL connectios as well.  To change that, use "hostnossl" in the penultimate line.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

pgsql-admin by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: Database schema changes tools
Next
From: Frank Gard
Date:
Subject: Re: proper pg_hba config to require ssl from non-local/private ips