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 1pzhpQ-000132-ID for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 17:54:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzhpP-0007v9-8N for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 17:54:15 +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 1pzhpO-0007sL-TF for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 17:54:14 +0000 Received: from mail-pf1-x42f.google.com ([2607:f8b0:4864:20::42f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pzhpL-000ZhL-Jv for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 17:54:14 +0000 Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-64cfb8d33a5so1357813b3a.2 for ; Thu, 18 May 2023 10:54:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684432450; x=1687024450; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=kpRceN8CxEJ3rv/nnfexFfgvtP+kg3SR+hU7ylEhUmI=; b=rDsaaukWi+Z/3hXVdyMcY9TJobDDUgGyrZE77tPwyNGq3P9LenY4RZU4t3zq42n/By Z5kiDaOxCwFVzGG7CVru6oMyW1MD0HyqzPdVSglqU20uOhlEDf4c51S7RE8YFApl9ZZW QjbsvHoqVvKKqyK+NeEf+qf1OgH3Gk1sIiZ7LWFZ2HA8yGddsE4w6JP9Rp2NJ7CIJxfJ ayo22r8LCDOrHUxvJmj5bZPU9xwngd1TdEUhImMYZJNSJmOg9i9PkhTwmlRUeWhqPJXf 7kvEO25UmyGG98RIjegmDSnst3tU+11oI0aCexMcbgD+F4HfgRFZmu1j3GZ3CZv+b7C3 aIWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684432450; x=1687024450; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=kpRceN8CxEJ3rv/nnfexFfgvtP+kg3SR+hU7ylEhUmI=; b=k88tgFMJ24p66G5cbNz5S+rR/73wIm/8fQwOn0FDH18p2uvgbhnDwX27y8OlMouWlg 8ZcVCyQhNZjfi8DKMgPHjtcTUgb4gfXHa1AyfFQjQFFF9BhI++JHotq8uHk/TL2zH3tT 68kFXxm53jojcu44rrjiWIJCB1vx91I0YM1h1Ko92Cvlr+Dysu1bGwUx8wa1sZs3UQOq R8rkuopw1+O9uG01FzyEHLvddxltaW/wVcanHBmoHRCLOfsJYjR481HqSDRciMNBJL2P 65rvjfpLWyS6RL2wTZTvnFc6UNtB4T53EhY3NlpVA1YZUQrvhyhdAKM89D+lYBruT2eo +Y3g== X-Gm-Message-State: AC+VfDxIzf7dXt/uWyFfjN7dwMErdmPAru6BaWFZeVHeuezNDrS2PbAM mMUDGxawq/NJtHYw1zJbGMP/foQ4syI= X-Google-Smtp-Source: ACHHUZ4smpRKAscvyi5lJW0ZSMTX/N+OmAc9Zoo89e8G1y7klynng0hyylmO0q/TpzP5HJvs5IwhPA== X-Received: by 2002:a05:6a20:a487:b0:109:c500:376c with SMTP id y7-20020a056a20a48700b00109c500376cmr526886pzk.12.1684432449538; Thu, 18 May 2023 10:54:09 -0700 (PDT) Received: from ?IPV6:2601:681:5a00:f790:2779:fd28:eff6:823f? ([2601:681:5a00:f790:2779:fd28:eff6:823f]) by smtp.gmail.com with ESMTPSA id r31-20020a17090a43a200b0024e07ae2cfesm1748228pjg.38.2023.05.18.10.54.07 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 May 2023 10:54:08 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------rskRkPc0S2OfRcMpFgUMBySd" Message-ID: Date: Thu, 18 May 2023 11:54:05 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: <08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com> From: Rob Sargent In-Reply-To: <08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------rskRkPc0S2OfRcMpFgUMBySd Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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." --------------rskRkPc0S2OfRcMpFgUMBySd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
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."

--------------rskRkPc0S2OfRcMpFgUMBySd--