Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qeHv1-006NwH-Cb for pgsql-general@arkaria.postgresql.org; Thu, 07 Sep 2023 16:31:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qeHv0-003Byb-Aq for pgsql-general@arkaria.postgresql.org; Thu, 07 Sep 2023 16:31:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qeHuz-003ByN-Kp for pgsql-general@lists.postgresql.org; Thu, 07 Sep 2023 16:31:45 +0000 Received: from tamriel.snowman.net ([70.109.60.50]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qeHut-003hvz-VY for pgsql-general@lists.postgresql.org; Thu, 07 Sep 2023 16:31:44 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id AF96C5F7BB; Thu, 7 Sep 2023 12:31:33 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snowman.net; s=dkim; t=1694104293; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3M/E6SKk9HRyf8kZcY0UdQSQhaebGI4aytIC/qDLkgk=; b=aYwb+SUebenqmsG3Ljddc5j3l0PxIInhbJaac3HrIpxk0mIzxX6YJlsgaFMYEP6mCHqONY gfW89Iym5lDRhlqMg6w/u/mDUm0U9FgNjQyZBRZV/XeH7B5kaZUn4BgT48BfhpLJ17jHPH 9KTQ0U1GVlxZeAUPjZKHsWTWvR4qv64= Date: Thu, 7 Sep 2023 12:31:33 -0400 From: Stephen Frost To: Ron Cc: pgsql-general@lists.postgresql.org Subject: Re: Will PostgreSQL 16 supports native transparent data encryption ? Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uBg9JAJ0gOza1srX" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.1.4 (2021-12-11) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --uBg9JAJ0gOza1srX Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Ron (ronljohnsonjr@gmail.com) wrote: > On 8/24/23 14:08, Stephen Frost wrote: > > * Ron (ronljohnsonjr@gmail.com) wrote: > > > On 8/21/23 18:49, Bruce Momjian wrote: > > > > On Mon, Aug 21, 2023 at 07:02:46PM +0300, Mostafa Fathy wrote: > > > > > It is mentioned here=A0https://www.postgresql.org/about/press/faq= /#:~:text=3D > > > > > Q%3A%20What%20features%20will%20PostgreSQL%2016%20have%3F=A0that = native > > > > > transparent data encryption is being worked on and it may be deli= vered with > > > > > PostgreSQL 16. > > > > >=20 > > > > > Is=A0PostgreSQL 16 beta version includes native transparent data = encryption or > > > > > not ? because I checked the docs=A0https://www.postgresql.org/doc= s/16/index.html > > > > > and couldn't find anything=A0related to transparent data encrypti= on. > > > > >=20 > > > > > If not supported yet in the beta version I would like to know if = PostgreSQL 16 > > > > > final=A0version will support=A0native transparent data encryption= or not? > > > > Not, PG 16 will not support it, and I am unclear if later major ver= sions > > > > will either. > > > That's disappointing, since TDE makes PCI audits that much simpler. > > There's ongoing work happening for TDE support and we'd love to hear > > from folks who would like to see it included. >=20 > PgBackRest currently encrypts it's binary backups. pgbackrest is optionally able to encrypt backups, sure, and that's certainly a good thing, though having a way for the process performing the backup to not be able to actually see the unencrypted data in the first place eliminates that as an attack vector. > 1. What kind of encryption would there be?=A0 AES256 makes the auditors h= appy. Supported options for AES would be 128, 192 and 256. > 2. Would TDE-enabled pg_dump create encrypted dump files? No, pg_dump is a client utility and hasn't got anything to do with TDE really. > 3. Would TDE obviate the need for PgBackRest's encryption? The short answer to this is 'probably yes, when TDE is enabled on the cluster'. Clearly, pgbackrest would continue to support encryption and there will be some things in PG that aren't encrypted that it might be nice to have encrypted, depending on your particular security folks, but you wouldn't need pgbackrest's encryption to ensure that the principle user data is encrypted. > 4. How would encrypted "pg_dump --format=3Dplain" work?=A0 Or could it on= ly work > with the other formats (which is fine by me)? pg_dump isn't impacted by TDE. > > You can expect an updated patch set for the September commitfest. >=20 > For that which will be Pg 17? Probably still optimistic to be thinking about this for PG17, but hopefully some of the preliminary work will be able to get into PG17 even if full TDE does not. > > Getting more folks to test it > > and use it and review it would certainly help move it forward. >=20 > By any chance, will binaries be created after the September commitfest?=A0 > (Hoops must be jumped through to get development packages installed on the > database servers I have access to, but I'd jump through them if needed.) This would be something to ask the package maintainers... but I tend to doubt they'd want the additional work; there's already lots and lots of packages they're dealing with and to add on packages for every patch that's posted to the PG mailing lists would be a huge task.. Thanks, Stephen --uBg9JAJ0gOza1srX Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEwf6gbxKhD863zrx/7WyKOINHZFUFAmT5+uMACgkQ7WyKOINH ZFX/ZQ//cExONNzZOEBiaCmg2AKqlzIGTBUXy4sKezHW4vgxhkfnYNFf1SCyFISP Cr5r2l7aqq3d8A+bTouSo2Hjb54O4lSxsItU7xoCNsaGQ5N5sDl5mczBsu1SirW2 qvu/YAP4JMiAFkln/7Ocs7wc3L/sT+7kEHCnG2s6tLrrTiQQs0h16mghOBNFPs// owiLxxXFax1xxsY4YgIWUJsP9tVooXiqqbNFQt3Jw8jJAWHI4UG0GSIbH/n1bSYM XGEuvCXw6609ADo9H7N7C/3DQDHvMVArup5/hoFMP2rOw0+BdDERAJcdx4TpLcdp zTGvDcRPHUdA74Ny7dNj4fry6LH9RjzQXT8XBfHP8U5DDnkmHf/97vHXO0SHQTNt 7Efujsf8jyYXHuuJ3tRW96yr96YTW257AvAPK8P3yAlOjxvVO0oiaCYnoAbaKHzw tmdBKOcGOOBldOkqqhPk2v2MoeFNz4oVG232ScZUAqjEypvq4Of00n0cDS8gHr8s k2++8sLY+a9mgTUGtuyyRqr6Vryaio6MM/btbE3++PzKF48FgaJmB4m+uQne7nS5 LEgqr+sz+1Sduz9TI3m2P+dA7Xgaj2r8Id1dkPPhwKKOZTUs9WNQXOAUzhUrbEeN knjhwB6cbVorPVanQ2iiyhOY5Oqy5lvEXVnQD5rno63vPwLum2s= =6Ewv -----END PGP SIGNATURE----- --uBg9JAJ0gOza1srX--