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 1kpZdf-0006kJ-2u for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Dec 2020 16:26:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kpZdc-0006fi-Hm for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Dec 2020 16:26:52 +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 1kpZdc-0006fa-Ah for pgsql-hackers@lists.postgresql.org; Wed, 16 Dec 2020 16:26:52 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kpZdX-0006RC-9H for pgsql-hackers@postgresql.org; Wed, 16 Dec 2020 16:26:51 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 4CB125F7A2; Wed, 16 Dec 2020 11:26:46 -0500 (EST) Date: Wed, 16 Dec 2020 11:26:46 -0500 From: Stephen Frost To: Michael Paquier Cc: Bruce Momjian , PostgreSQL-development , Masahiko Sawada Subject: Re: Proposed patch for key managment Message-ID: <20201216162645.GO16415@tamriel.snowman.net> References: <20201215031902.GB14596@momjian.us> <20201215190909.GK16415@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="T4rzSMN49s5g0op0" 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: Precedence: bulk --T4rzSMN49s5g0op0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Michael Paquier (michael@paquier.xyz) wrote: > On Tue, Dec 15, 2020 at 02:09:09PM -0500, Stephen Frost wrote: > > Yeah, looking at what's been done there seems like the right approach to > > me as well, ideally we'd have one set of APIs that'll support all these > > use cases (not unlike what curl does..). >=20 > Ooh... This is interesting. What did curl do wrong here? It is > always good to hear from such past experiences. Not sure that came across very well- curl did something right in terms of their vTLS layer which allows for building curl with a number of different SSL/TLS libraries without the core code having to know about all the differences. I was suggesting that we might want to look at how they did that, and naturally discuss with Daniel and ask him what thoughts he has from having worked with curl and the vTLS layer. Thanks, Stephen --T4rzSMN49s5g0op0 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJf2jVFAAoJEO1sijiDR2RVGqkP/A+o5J/k5RWsc/ZUMUVOELFy Gc4uuqB16l9iuIE2j9ZnAsQLN+LQACZ05TFjoaqK6gHAba+GfRM+9TlR9edwivKe PYYokOBUlJmkgbgUyK930EH0wEVeOV5Bx1GZm6dndxnHVyk3xIOwAxMdRbnRqcT0 1yNgD83IMxM63doCxWmn+AR+cYqZhg8Bd8znmjmL+juOHHG7+Sww66/xl+5qyKeD EFUM/WKlNggrW/Yk17/GLITKzPqDPg7ZAxfS9E6vzDrHcR8+y2N42nV4lWb0rs7a iK2eQTU+l5UjlF181YxxVmV6AQPCzteVTT4NwAVTMZStA9WEnXvBY5IrSG9D586G +crhxQd5/+sfJdzmVhCj7B7C9NzbpV1h4/28RkIevvR32jo/aJZjgWtdNaRWXP4q EeasQ45xDb9netq7ZAf9xzQIj60jYyV0rVv9EImFfnidI/Lp3X3RvBfB7J6AG3gT nFteLCgGQga9PxlzhQlcnJtNYta0oG7xsv57BP6tV4tyljGtppG3Ot0iOntHXkAZ 4tk3MSr88Mzj8kbagA5xkB2RvGfElKs8M0TCQRc9Gdnt27DxvQN3l43s3BY5k7DR 2+9i0F9y/d1mYyk9h3QQHiwzGNMenZLmyGEQkZOvgjWU1QQW4zoNiG5K6y6Vqbdv 1aK18qFOzGGcp6pVhJzQ =xma9 -----END PGP SIGNATURE----- --T4rzSMN49s5g0op0--