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: Thu, 18 May 2023 13:56:48 -0500
Message-ID: <1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com> (raw)
In-Reply-To: <f714e518-374a-8d74-1119-9a363857a367@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>
On 5/18/23 12:54, Rob Sargent wrote:
> On 5/18/23 11:49, Ron wrote:
>> On 5/18/23 10:54, Stephen Frost wrote:
>>> Greetings,
>>>
>>> * Tony Xu (tony.xu@rubrik.com) wrote:
>>>> The FAQ (copied below) mentioned that native transparent data encryption
>>>> might be included in 16. Is it fair to assume that it will support database
>>>> level encryption, that is, we can use two encryption keys for two databases
>>>> in the same server, respectively? How can one verify that?
>>> The current work to include TDE in PG isn't contemplating a per-database
>>> key option. What's the use-case for that? Why do you feel that you'd
>>> need two independent keys?
>>
>> I don't /feel/ that key-per-database us useful; I /know/ that
>> key-per-database is useful, since the databases can be different projects
>> for different companies. Each wants it's own encryption key so that no
>> one else can get to their at-rest data.
>>
>> (pg_dump files will automatically be encrypted, right?)
>>
>> --
>> Born in Arizona, moved to Babylonia.
> Ron, this sounds like a revenue opportunity: "Oh you want your own key,
> well then we'll have to spin up another server just for you so you're all
> separate and special-like. Way more secure that way."
We need to keep costs down, too.
Oracle (I think) does it at the DB level, and so does SQL Server. Upper
Management hears us say "sorry, no can do" and wonders what bunch of
amateurs are developing PostgreSQL.
--
Born in Arizona, moved to Babylonia.
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: <1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@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>
* 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