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 1lRy6X-00053i-8R for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Apr 2021 14:15:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lRy6W-0004c9-5e for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Apr 2021 14:15:24 +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 1lRy6V-0004c2-VG for pgsql-hackers@lists.postgresql.org; Thu, 01 Apr 2021 14:15:23 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lRy6P-0006Lj-J1 for pgsql-hackers@lists.postgresql.org; Thu, 01 Apr 2021 14:15:23 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id E95CB5F799; Thu, 1 Apr 2021 10:15:15 -0400 (EDT) Date: Thu, 1 Apr 2021 10:15:15 -0400 From: Stephen Frost To: Michael Paquier Cc: Jacob Champion , "daniel@yesql.se" , "pgsql-hackers@lists.postgresql.org" , "hlinnaka@iki.fi" , "andrew.dunstan@2ndquadrant.com" , "thomas.munro@gmail.com" , "andres@anarazel.de" Subject: Re: Support for NSS as a libpq TLS backend Message-ID: <20210401141515.GR20766@tamriel.snowman.net> References: <05da9d530ab01e6959bd50c993d590ad73575c21.camel@vmware.com> <20210324170036.GS20766@tamriel.snowman.net> <8f741a425fd135ca38a28063730715499f7f6445.camel@vmware.com> <20210324181016.GU20766@tamriel.snowman.net> <50c5a423329ea9996a2a2b167931711189ed5d1b.camel@vmware.com> <20210326193337.GW20766@tamriel.snowman.net> <60817900d55ea2c9b8dd94658efd2d2adb76dd67.camel@vmware.com> <20210326220540.GZ20766@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="K4nQHLatfJZSBuQI" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --K4nQHLatfJZSBuQI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Michael Paquier (michael@paquier.xyz) wrote: > On Wed, Mar 31, 2021 at 10:15:15PM +0000, Jacob Champion wrote: > > I think we're going to need some analogue to PQinitOpenSSL() to help > > client applications cut through the mess, but I'm not sure what it > > should look like, or how we would maintain any sort of API > > compatibility between the two flavors. And does libpq already have some > > notion of a "main thread" that I'm missing? >=20 > Nope as far as I recall. With OpenSSL, the initialization of the SSL > mutex lock and the crypto callback initialization is done by the first > thread in. Yeah, we haven't got any such concept in libpq. I do think that some of this can simply be documented as "if you do this, then you need to make sure to do this". Thanks, Stephen --K4nQHLatfJZSBuQI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJgZdVzAAoJEO1sijiDR2RVqg8QALomgKlrx+sTBVsIv3Ht48dF 8wirb62UBt1f6aFTVRuQGUZ2yLcxlkepm7THVbWdWxyu1mXMD1pOBAgeOU//3aJH Mht/ZGJxz9BcpaMyJHHFX8wCLKkxJyiJmGKyBQ27AaKv8oYl1uIo4X4BoHTw2Upu Nb0sO2Bgev9sAMTNFOJbV6kh+JZbwZE89w1uSi4ettTdBrm4l2r+xOxj1RUZQf36 fJD7XHvdZ/wMcSULihBdF9EQuUuGnvhxhZ4X0BycBhGfTJHjJ0Jedx9AnFVeZLyq 8XNwsAnDSpw3XPOGb54sybJ2LJBW6sq8w/Q5BfolcpaxGRzoPMyp4Kh6kcyup5Qe CQ8hM5WJPHw/E9cV+wLklQNBP7X02ToHLL7tyTDy4x1QGcCzzDhSJT9HgGN2CpkS AqUl4vW9VRS8yjko7srtf813yH3JtXrIZcEbbN7Ddbd6RtxH2tq9Cd6nuWw2/DGn 71QB5KnvAGjPt7Cby1su1f9B5UP6UV1ntY8K8PJM3A3ISsAjVltxfUTCfQCxYoVi RpqF2GYwWxDmWrFjIFC0ycj7rMn0PfiUM7tLT2Fy+qZycPxBsk+soQ0LWYrYiJCy J8zdvknhPTDCUMojNNpQjhK0jHM5+BoFnpGZqNliiABECqwRgq9Q1XDY3Qm3t3Z6 p4KQVj0CsMMucfmjJtW7 =Iq5z -----END PGP SIGNATURE----- --K4nQHLatfJZSBuQI--