Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qZcW4-0069q7-9m for pgsql-general@arkaria.postgresql.org; Fri, 25 Aug 2023 19:30:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qZcW3-005STW-7k for pgsql-general@arkaria.postgresql.org; Fri, 25 Aug 2023 19:30:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qZcW2-005STI-TM for pgsql-general@lists.postgresql.org; Fri, 25 Aug 2023 19:30:42 +0000 Received: from mail-yw1-x1131.google.com ([2607:f8b0:4864:20::1131]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qZcVz-0011xK-5a for pgsql-general@lists.postgresql.org; Fri, 25 Aug 2023 19:30:42 +0000 Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-58d31f142eeso15649097b3.0 for ; Fri, 25 Aug 2023 12:30:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692991837; x=1693596637; h=content-transfer-encoding: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=lCkLZVpINwyhrQan6QnP06OxIThD6/ZoEkWVKI+TzOQ=; b=MynM/O43qNKoi8drJZftz2aQvThHyNFJCFYRYHPmuu0fc+dS8TFJ1deo+HKrd7z+ub t8mpfNoDmh38ZDLLIQR5aqQItHJvgNaZbczurzJ7ojHcNk8mGphxVczBs0QV5CVqbc6L 84omOlCe/neOawzDf26d2RrxUDGtG0xS/wbasrArbN4n1heGBzET+rzq5gW0bKcrTw75 0U9siqV1XTEmIYgEA4RPALP7TAwrW0XBX6ksuk/yRdLrFik5hc09TH1Jh9+ndw2O4EFx P37Y74w3FmkFREn/zVann5XKMNmwuzQbSmZYgk2rcvluReulf54dg3K1Cz3ZCbWQMXlE rhTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692991837; x=1693596637; h=content-transfer-encoding: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=lCkLZVpINwyhrQan6QnP06OxIThD6/ZoEkWVKI+TzOQ=; b=bQNz1PPTdaah3dbPYttvBc+LYA7Z2uj+DpoC98dkPPufORNXq40ufnfuEfEhGstVrQ oMl2NXl6l2+G4aF6RGIN+93I3vKCUJWMxnlp6UrejhQffRE/yiZ2DEJ3gDqTZZGKxZVS HG4HXkgjZt/DcgH1eeB/0U0LsBRgVCKVspL38h5nqHdQmor/N+fyKciGZH+qmitn4yqX teMzpzzGoySwtnEerqdhcwE4E+hjOTWOyQj0B8k4OZcuZGfHg2MAH2dpecOqOosTBuvC GxKqhhGbNXIfKge9IoJY3/MP1wCF517NfylYopLqdBKX6F7XXX4pvt7xKnkMOrevyhNl 0f7Q== X-Gm-Message-State: AOJu0YzMeaYaFxsFiNsuZ4wb1U5e5bnEjLXih0Fx5ndGprsvAeaio+8l IEHyWrLNemWRl/w7ZscVY81ql6kpAsQ= X-Google-Smtp-Source: AGHT+IF1AG6/BfLtMdoo9XizE8cO9z/t5WaaTE0roIyrPp+RjhkeZw2ojZjhPFRX81sQDqKesKwWSg== X-Received: by 2002:a05:690c:e09:b0:592:95c7:bff6 with SMTP id cp9-20020a05690c0e0900b0059295c7bff6mr4319393ywb.31.1692991837288; Fri, 25 Aug 2023 12:30:37 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:6c2f:4566:50e3:7edf? ([2600:1700:bd2c:b810:6c2f:4566:50e3:7edf]) by smtp.googlemail.com with ESMTPSA id x67-20020a81a046000000b005922c29c025sm651231ywg.108.2023.08.25.12.30.36 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Aug 2023 12:30:36 -0700 (PDT) Message-ID: Date: Fri, 25 Aug 2023 14:30:35 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Will PostgreSQL 16 supports native transparent data encryption ? Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/24/23 14:08, Stephen Frost wrote: > Greetings, > > * Ron (ronljohnsonjr@gmail.com) wrote: >> On 8/21/23 18:49, Bruce Momjian wrote: >>> On Mon, Aug 21, 2023 at 07:02:46PM +0300, Mostafa Fathy wrote: >>>> It is mentioned here https://www.postgresql.org/about/press/faq/#:~:text= >>>> Q%3A%20What%20features%20will%20PostgreSQL%2016%20have%3F that native >>>> transparent data encryption is being worked on and it may be delivered with >>>> PostgreSQL 16. >>>> >>>> Is PostgreSQL 16 beta version includes native transparent data encryption or >>>> not ? because I checked the docs https://www.postgresql.org/docs/16/index.html >>>> and couldn't find anything related to transparent data encryption. >>>> >>>> If not supported yet in the beta version I would like to know if PostgreSQL 16 >>>> final version will support native transparent data encryption or not? >>> Not, PG 16 will not support it, and I am unclear if later major versions >>> will either. >> That's disappointing, since TDE makes PCI audits that much simpler. > There's ongoing work happening for TDE support and we'd love to hear > from folks who would like to see it included. PgBackRest currently encrypts it's binary backups. 1. What kind of encryption would there be?  AES256 makes the auditors happy. 2. Would TDE-enabled pg_dump create encrypted dump files? 3. Would TDE obviate the need for PgBackRest's encryption? 4. How would encrypted "pg_dump --format=plain" work?  Or could it only work with the other formats (which is fine by me)? > You can expect an updated patch set for the September commitfest. For that which will be Pg 17? > Getting more folks to test it > and use it and review it would certainly help move it forward. By any chance, will binaries be created after the September commitfest?  (Hoops must be jumped through to get development packages installed on the database servers I have access to, but I'd jump through them if needed.) -- Born in Arizona, moved to Babylonia.