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 1pzio4-0003JA-0Z for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 18:56:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzio2-0003HV-Ms for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 18:56:54 +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 1pzio2-0003HL-B1 for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 18:56:54 +0000 Received: from mail-yw1-x112f.google.com ([2607:f8b0:4864:20::112f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pziny-000aCx-NZ for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 18:56:53 +0000 Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-561c9635241so29934417b3.3 for ; Thu, 18 May 2023 11:56:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684436209; x=1687028209; 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=nS11t6P7ZJe3r5vQaiFdC6XGyl/25dRpGqX/6mQIb/g=; b=dxdf5/fCUxpg3t9r4GjfuaOf1n8CW+iuepnDa7Yi6CZvexLqU/WUUHEFn7DFE0ow1+ 1lHmrxWIPZIOYHjSNEnQayt4X7pMyz43LInp63X+9LpsBDKfRuckxK2whkmAH01VIlSZ NUrJaHw7+2vox04dpEMNT75R+Ap1IdspxM2Lw6IdCNpf+lw7uhRjVzmYCSmJW7v6PNg+ uJNbEYngpvGx6XP34vPBo8ZxpcKwR1bOdz46OqGCVBzMMckVvfKBiRWpyJsfB8X4phWU eHYQcvuUv9u85bjws3lhQvGX9GY24TCXYbAw3xMcgzwPItCI4q4xxRR/nEbJEGvR39Rn c5Ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684436209; x=1687028209; 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=nS11t6P7ZJe3r5vQaiFdC6XGyl/25dRpGqX/6mQIb/g=; b=gW3eLlRsgI1vWHeNan87EdIJFGfeouOoSaJDcd7M37HYhe0MsJ2ZOkfnzZyy5YdPSG LzV9MyoIi69Xezj32Ybty3CrJeua0ykCJRIEfeb+bTYa2d9P0rhgdqcA+6BIK2GtrZgQ PFlcEYgwaJikgBB4v3TiLM+9sfs7oxLloNjBC8Z0gPQNtSDp83RPjqGZFjjixK0V7/eo EGKXBj9eqXWXJcZRNDUS/AbF32J70cSPA9Zynr4XfoJmeK55a1p7pjvgI5XsQWOnPzAS pkRz43W/HoEGtTsqdSEP2vwdZE/Ys8fWf711gpDhLdGpAy5z4lp/qW4J9YpWuGKGsnyp jUFw== X-Gm-Message-State: AC+VfDyKkd6/d5RhRk7mD656Qy3vOCB1g8z32OUXIKlYx0lylKjJ1R7+ O31NJ5EFQHSvXyWYRybiyilwr7hhyqI= X-Google-Smtp-Source: ACHHUZ7wrjxRtGvTfPSZkDchcez8XGxVRPiOcjAz17FFUeAwd+mcypbCao+i9EYI7zNQxEu3xxtxdw== X-Received: by 2002:a81:84d7:0:b0:561:949d:a7fd with SMTP id u206-20020a8184d7000000b00561949da7fdmr2145903ywf.45.1684436209462; Thu, 18 May 2023 11:56:49 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:1894:39f8:bd0e:1dc4? ([2600:1700:bd2c:b810:1894:39f8:bd0e:1dc4]) by smtp.googlemail.com with ESMTPSA id z70-20020a0dd749000000b00559d9989490sm610782ywd.41.2023.05.18.11.56.49 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 May 2023 11:56:49 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------Iyz8iZlRkBIkpRGkpVAaVJIZ" Message-ID: <1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com> Date: Thu, 18 May 2023 13:56:48 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com> From: Ron In-Reply-To: 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. --------------Iyz8iZlRkBIkpRGkpVAaVJIZ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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. --------------Iyz8iZlRkBIkpRGkpVAaVJIZ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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.
--------------Iyz8iZlRkBIkpRGkpVAaVJIZ--