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 1oHIo2-0008E8-Bo for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Jul 2022 05:45:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oHIo0-0005cT-UU for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Jul 2022 05:45:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHInz-0005WD-IT for pgsql-bugs@lists.postgresql.org; Fri, 29 Jul 2022 05:45:00 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHInw-0003HI-Hv for pgsql-bugs@lists.postgresql.org; Fri, 29 Jul 2022 05:44:58 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 0136B5C013E; Fri, 29 Jul 2022 01:44:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 29 Jul 2022 01:44:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1659073494; x=1659159894; bh=Hk7WYb/teS N/PHbmwRxxqWsB6WPJskjPLTqF3kfOZ50=; b=CdMxpNN4BifEqdop9yPqyoiPyy RfqX/xIiw3+6P2i0kO3g1OacsjqUMTIARHR6IymwKvqWzCIU+Gu/jMCs1QBl6U1V yrqfQc7LiWOjMuamvJPoPpcLizXFPkHw9jMRlZyJrh4RaCTmzBTlAywkWQMbZIXH 6DYbic/gxjLhEaJtfk7fKebGwFht1PnTlfuMTGqbMQFNKsPkd3fCaS+o2vqFxjWM 9FEBMm++fzSruSV/rUinQLs9shnAoB7ymRpYYI3lt8GPfTB32LizmrzrTanFU/pE X3kEBnp+A+MsK6IPRL006l3O8BeVVt3orva7k8BR8JLQRZXt1yGuO/R0BwRQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1659073494; x=1659159894; bh=Hk7WYb/teSN/PHbmwRxxqWsB6WPJ skjPLTqF3kfOZ50=; b=2c/ClG6zfpXSQOZ0qxP+gn2jERqCXR+vSMWSD5NvB693 2hfI6aI6+UnY/d3GgYBSEMH/wG7ZwLx04iH3HBYNy+A0jL2X/W99Qayr20rQpvRy DKQEjlMea/PFU7VzrjKw+tkm7gglsroaLUn5vhP9IdXMk4i9W+aId7L0s80QIlIE BFhP3Vlr6wQxxHG3rZsJ/GYRROjq8KUUj4E/lfzcr+/oqgchA3BuFgV6Or6htTLK csZGDC3zB9Ni492CYYIoNP14Lm62r+E2uZ8CHNB6YqcNlr9uNusvNuVqVQXUteW4 8/KLOt2PEn0hMbTYJNDHc+yFSvriyA1eQa7Hqa6hmQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdduiedggeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlvdefmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepfeevveetudfhffduffdvtdej keeivedufefftdegtefgffeftdfhjedvgeeljeehnecuffhomhgrihhnpehivghtfhdroh hrghdpghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 29 Jul 2022 01:44:52 -0400 (EDT) Date: Fri, 29 Jul 2022 14:44:47 +0900 From: Michael Paquier To: * Neustradamus * Cc: "pgsql-bugs@lists.postgresql.org" , Jacob Champion Subject: Re: RFC 9266: Channel Bindings for TLS 1.3 support Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BwcyBwH5G0F9acWp" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --BwcyBwH5G0F9acWp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Thu, Jul 28, 2022 at 08:33:50PM +0000, * Neustradamus * wrote: > Can you add the support of RFC 9266: Channel Bindings for TLS 1.3? > - https://datatracker.ietf.org/doc/html/rfc9266=20 >=20 > Little details, to know easily: > - tls-unique for TLS =3D< 1.2 tls-unique is not planned, as we have already tls-server-end-point for TLS1.2 and Postgres requires a certificate, anyway. > - tls-exporter for TLS =3D 1.3=20 >=20 > It is linked to: > - https://github.com/postgres/postgres/search?q=3Dtls-unique So, tls-exporter has been made an official thing, finally. I was wondering when this was going to happen. Jacob Champion has given me a patch to support that, based on OpenSSL's SSL_export_keying_material() to do the job. The base integration is not complicated, but I still need to think a bit more about it when it comes to the min/max TLS protocols we allow in libpq, for example, and polish the whole with tests. We don't force any failures depending on the other connection parameters for tls-server-end-point, so I suspect that we should be fine with keeping things at their simplest. I should be able to get something sent to the mailing lists for the commit fest of September, so as we could have this feature in v16~. -- Michael --BwcyBwH5G0F9acWp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmLjc88ACgkQnvQgOdby QH17sg//a7Ix+0nRxcRRxTnAvF+Fx/glS/CrMzeuU/sJ0ZRoWoJZhr60NdsiS6wH uJXTSjEmgqHp4uzdnoCjNFY0zBHFN82AqOAjVrNR1hTZdQera/QvEsWMt1Uypt6y SgvJsWmM5/MOQIlLjMj9NUraTg1CI2oGk5G+wTFLe0i49ZTYkwRVU8Zc/jOWqNwi sgcWCEf4XxJUtt0iBocInRxIBDWOajbICCizHn8hddV78qP49q0/tc2OQX6/zW8j oK2N3fuCviv8SNlfXSl3mwuTPO0roC0qotAIRSrOSm6Ha0H/U1nSFErzFmZnq8we sqjqTfNQGpjjltl8b7M+J3j3B9xLMIPDkpGk9jYVbJawfPfUco4vZ3r0HC86Qp1R 0wv6wH8RG7CwuDr9xnWU4bfhM3YVRAPulbtW3vTNitzrEa1QNBJh93K7C5smwU/w xisyUPjmDYeKbX5QE2VQsRRpQvLZo+svIt3blfk2rb6q/phQaC5mYRT8ZF0CNLn2 8GuDKYqbc1AQj2yfG5EZowF5lFW4OjbHqbD43pF0wVO3wxeeCgqUo2Kg9hwJnYoY lAFvR0q1bf7GlRPfteGgev/VBrSqFA1Qnx95fDj8PSIwihVbzwNLzyjieqjDsE9h Dy6h5vbDeHOqfRpx5RLYrFGQFJX3xXahoAi0XC5fA2nXA2IP4QY= =qEbR -----END PGP SIGNATURE----- --BwcyBwH5G0F9acWp--