From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Matthew Lenz <mlenz@nocturnal.org>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: proper pg_hba config to require ssl from non-local/private ips
Date: Wed, 19 Oct 2022 10:41:41 -0600
Message-ID: <E7513C58-F643-41B0-9EFD-EA8455B36553@elevated-dev.com> (raw)
In-Reply-To: <CANpBAJv81XXimKZCnv-u2yBGw6LyTTW7Y6eyUBZUwcMKa=unZw@mail.gmail.com>
References: <CANpBAJtuxCRnqvixsMFK-D7G=T6T_ma-Xef62saLR8doCW+tRw@mail.gmail.com>
<CAMkU=1zmeaZrLziKiYB62weDDMtQ1MpBb-6ja3M4=7D5HoSZmQ@mail.gmail.com>
<CANpBAJv81XXimKZCnv-u2yBGw6LyTTW7Y6eyUBZUwcMKa=unZw@mail.gmail.com>
> On Oct 19, 2022, at 10:29 AM, Matthew Lenz <mlenz@nocturnal.org> wrote:
>
> I didn't say the client was meant to enforce it. I meant the server should be enforcing it (it's not).
Doesn't really make sense for the server to determine client verification of server certificate.
1) Server controls what certificate is provided, thus has control over what CA is used.
2) What would it mean for server to turn OFF client verification? Server is allowed to say "here's my cert, doesn't matter that it's using a bogus CA, you take it regardless of your local settings"???
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, mlenz@nocturnal.org, pgsql-admin@lists.postgresql.org
Subject: Re: proper pg_hba config to require ssl from non-local/private ips
In-Reply-To: <E7513C58-F643-41B0-9EFD-EA8455B36553@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox