pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Date: Mon, 22 May 2023 15:37:29 -0500
Message-ID: <c8d52dc9-0be3-0a23-11f4-d0236e6a95e6@gmail.com> (raw)
In-Reply-To: <ee30dd66-a85d-526e-c1fa-a966732d3a1c@aklaver.com>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com>
	<ZGZKN0fQORPPNqc5@tamriel.snowman.net>
	<08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com>
	<f714e518-374a-8d74-1119-9a363857a367@gmail.com>
	<1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com>
	<5d617fb4-a2de-f6a2-f0d3-8a068ac4d83f@aklaver.com>
	<CADX_1abemND-2kO4sc8erSTr=WdP96Wp2onZfKbE2f+VYrP4CA@mail.gmail.com>
	<a3a68610-1b16-1ef5-11cd-2d191faec868@gmx.net>
	<CADX_1abAcP60kOA2U-b4oj5KGgJqSoLxYDR731L2YHcANZsNEw@mail.gmail.com>
	<CACufLfwDbvsF9d_AxZb1Co0SJJB2XnCYuwQ5+FhVtGF3VYBQmg@mail.gmail.com>
	<78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com>
	<CACufLfxmdhgth+2J7jEktkqjMDHKVhDdzZtJERiOnAd9Md8sSA@mail.gmail.com>
	<fc6caca1-017e-3691-0375-ede50cadc89c@gmail.com>
	<ee30dd66-a85d-526e-c1fa-a966732d3a1c@aklaver.com>

On 5/22/23 15:06, Adrian Klaver wrote:
> On 5/22/23 12:38, Ron wrote:
>> On 5/22/23 14:22, Tony Xu wrote:
>
>> RDS Postgresql would do the job just fine.  And since you can't get to 
>> the files (only access it via port 5432 and aws cli/web, there's no need 
>> for TDE.
>
> As I understand TDE whether you can get to the files is not really the 
> point. It is that someone/thing can and if they do the files are 
> encrypted. Pretty sure RDS is not magical enough to have no access from 
> any source to the file system.

They sure hide the raw files well, only allowing access from very restricted 
paths (port

Or maybe we just locked it down tight.

-- 
Born in Arizona, moved to Babylonia.





view thread (36+ messages)  latest in thread

Message-ID: <c8d52dc9-0be3-0a23-11f4-d0236e6a95e6@gmail.com>
Permalink:  ../c8d52dc9-0be3-0a23-11f4-d0236e6a95e6@gmail.com/
Also on:    postgresql.org/message-id/c8d52dc9-0be3-0a23-11f4-d0236e6a95e6@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
  In-Reply-To: <c8d52dc9-0be3-0a23-11f4-d0236e6a95e6@gmail.com>
  References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com> <ZGZKN0fQORPPNqc5@tamriel.snowman.net> <08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com> <f714e518-374a-8d74-1119-9a363857a367@gmail.com> <1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com> <5d617fb4-a2de-f6a2-f0d3-8a068ac4d83f@aklaver.com> <CADX_1abemND-2kO4sc8erSTr=WdP96Wp2onZfKbE2f+VYrP4CA@mail.gmail.com> <a3a68610-1b16-1ef5-11cd-2d191faec868@gmx.net> <CADX_1abAcP60kOA2U-b4oj5KGgJqSoLxYDR731L2YHcANZsNEw@mail.gmail.com> <CACufLfwDbvsF9d_AxZb1Co0SJJB2XnCYuwQ5+FhVtGF3VYBQmg@mail.gmail.com> <78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com> <CACufLfxmdhgth+2J7jEktkqjMDHKVhDdzZtJERiOnAd9Md8sSA@mail.gmail.com> <fc6caca1-017e-3691-0375-ede50cadc89c@gmail.com> <ee30dd66-a85d-526e-c1fa-a966732d3a1c@aklaver.com> <c8d52dc9-0be3-0a23-11f4-d0236e6a95e6@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox