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 1ov1mg-0001dZ-9K for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Nov 2022 19:39:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ov1mf-0003r8-5V for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Nov 2022 19:39:49 +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 1ov1me-0003q5-Qw for pgsql-hackers@lists.postgresql.org; Tue, 15 Nov 2022 19:39:48 +0000 Received: from mail-oo1-xc29.google.com ([2607:f8b0:4864:20::c29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ov1mY-0004YS-BU for pgsql-hackers@postgresql.org; Tue, 15 Nov 2022 19:39:48 +0000 Received: by mail-oo1-xc29.google.com with SMTP id q2-20020a4a3302000000b0049ee5fe3ab7so2177184ooq.8 for ; Tue, 15 Nov 2022 11:39:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=crunchydata.com; s=google; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=FmwkC7zJ5BAwTfWs0XempPkHUzl9uxqPDaiQNpD6nFI=; b=IDJgtzkxb6AOvrx0yoBin/yKmdQ9iIGFchtuKEZfS96y12D5w0lYfQRBtbwUpxZP6U WbFV/bVJZ2T92SN6bDQ4ufxMa4h8ZL/cXwFD6G7dYf+9eC0pIRWVD2jkdQCF3EVRk7NY 4YpqTM0/Y1fXScYHntT1IiO8TbQCUlXOWHU+OVEz9bbxfYV1MTLZu9Notwx9Io2CWFgi Fp6T6+P3oSV8Hy8fDwApDE7vBAuW/8N2r4fnMMekgBJ7lnUneE309h4F0BzVXKF5AXfK AXGkt7h0Uj3qvBM3sSkynbKcouhbTLtBSd502RMvRaBHfaCTrQ1c75Fmm8hQkufIfWqy jJQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=FmwkC7zJ5BAwTfWs0XempPkHUzl9uxqPDaiQNpD6nFI=; b=ZJOQhwycyp2aeU0J8XUhJxiXpOVxu1e45Z/dwUGGMIOycW8JyJ5mdM9cHhAvNzP2VN LBE5jwvI+Zlna0dtlLTwSrQ7ioJ4IGraa4qhDEuri54onnw2P4j0qRpWm+KYYWfHtlD0 sT8MZ6SkeyIGexXZterNlwShjvk1fLBegKdhKDtwUq2fIj6U0OJFc8TUGdSS6wtvNQ42 fbr5FVhOm5VedaOpBcxP8HftvL+g99iyqNYY6FEcKS7hTMapRGAnmqYQuLK4C0HWPL/P xitaUlATcOu/KUE/euldnyuKy18xWjA4yEPBGif7sU8xbC4bx0qlFnC1ivPZG1pjq+pY GMYQ== X-Gm-Message-State: ANoB5pk5L0zPHJQ8xfnbUYseHrQAhnLkRyZKDEXkiRMM+xlopi8/6iEp RHjUEDK0Z3/P4lxr+aBd+sI+XCYQPi3Xvk/i X-Google-Smtp-Source: AA0mqf6o27lpR6b+hi9/nbZUhFW/NC4RhUjvENo4zNxaiDjjnGQvvcWrR5x9gBMJgJ/Rwlwus9sFOw== X-Received: by 2002:a4a:88c9:0:b0:49d:5cb8:4b01 with SMTP id q9-20020a4a88c9000000b0049d5cb84b01mr7964719ooh.65.1668541179695; Tue, 15 Nov 2022 11:39:39 -0800 (PST) Received: from smtpclient.apple ([2600:1700:5ac0:aa80:ed5b:b080:910a:8cec]) by smtp.gmail.com with ESMTPSA id a97-20020a9d266a000000b0066c2e241a4csm5762741otb.20.2022.11.15.11.39.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 15 Nov 2022 11:39:39 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: David Christensen Mime-Version: 1.0 (1.0) Subject: Re: Moving forward with TDE Date: Tue, 15 Nov 2022 13:39:27 -0600 Message-Id: References: Cc: PostgreSQL-development , Stephen Frost In-Reply-To: To: Jacob Champion X-Mailer: iPhone Mail (20A371) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Nov 15, 2022, at 1:08 PM, Jacob Champion wrot= e: >=20 > =EF=BB=BFOn Mon, Oct 24, 2022 at 9:29 AM David Christensen > wrote: >> I would love to open a discussion about how to move forward and get >> some of these features built out. The historical threads here are >> quite long and complicated; is there a "current state" other than the >> wiki that reflects the general thinking on this feature? Any major >> developments in direction that would not be reflected in the code from >> May 2021? >=20 > I don't think the patchset here has incorporated the results of the > discussion [1] that happened at the end of 2021. For example, it looks > like AES-CTR is still in use for the pages, which I thought was > already determined to be insufficient. Good to know about the next steps, thanks.=20 > The following next steps were proposed in that thread: >=20 >> 1. modify temporary file I/O to use a more centralized API >> 2. modify the existing cluster file encryption patch to use XTS with a >> IV that uses more than the LSN >> 3. add XTS regression test code like CTR >> 4. create WAL encryption code using CTR >=20 > Does this patchset need review before those steps are taken (or was > there additional conversation/work that I missed)? This was just a refresh of the old patches on the wiki to work as written on= HEAD. If there are known TODOs here this then that work is still needing to= be done.=20 I was going to take 2) and Stephen was going to work on 3); I am not sure ab= out the other two but will review the thread you pointed to. Thanks for poin= ting that out.=20 David