Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olC8g-0004wP-ES for pgsql-admin@arkaria.postgresql.org; Wed, 19 Oct 2022 16:41:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1olC8e-0008CH-Oq for pgsql-admin@arkaria.postgresql.org; Wed, 19 Oct 2022 16:41:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olC8e-0008C8-EW for pgsql-admin@lists.postgresql.org; Wed, 19 Oct 2022 16:41:52 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olC8b-0008MP-Im for pgsql-admin@lists.postgresql.org; Wed, 19 Oct 2022 16:41:52 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 9EF2C65E6E; Wed, 19 Oct 2022 16:41:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at emo07-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo07-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrDz4wNSduzR; Wed, 19 Oct 2022 16:41:42 +0000 (UTC) Received: from smtpclient.apple (unknown [165.140.184.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 46EEF6520C; Wed, 19 Oct 2022 16:41:42 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: proper pg_hba config to require ssl from non-local/private ips From: Scott Ribe In-Reply-To: Date: Wed, 19 Oct 2022 10:41:41 -0600 Cc: pgsql-admin Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Matthew Lenz X-Mailer: Apple Mail (2.3696.120.41.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Oct 19, 2022, at 10:29 AM, Matthew Lenz = wrote: >=20 > 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"???=