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 1qYJNK-001L1W-Sz for pgsql-general@arkaria.postgresql.org; Tue, 22 Aug 2023 04:52:18 +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 1qYJNJ-00E2Pn-C2 for pgsql-general@arkaria.postgresql.org; Tue, 22 Aug 2023 04:52:17 +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 1qYJNJ-00E2OT-0C for pgsql-general@lists.postgresql.org; Tue, 22 Aug 2023 04:52:16 +0000 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qYJNF-000IuW-9z for pgsql-general@lists.postgresql.org; Tue, 22 Aug 2023 04:52:16 +0000 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-58d70c441d5so45905377b3.2 for ; Mon, 21 Aug 2023 21:52:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692679931; x=1693284731; 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=FNvGqniYSJ51QuMFs79RM9uWOUFIvqo2X339VZOfyME=; b=kIoeEaZntT/qDOGc4g6VzA+dzK4W+5kq1Thgris1ybQIQkMhV+dmnKXymJf26dOO70 Wws0896k4qYD1Tk4PO+CDhL6/Y/ryeYcggjfuF8tWk2OtEpxe1fSkNR2ponN9RnHeKDv u3hePvODn1fgb2gK8xGuk7M1u1fdnQ2gpx9v2FbNe8eq1VFl8Q1bozE2ZH13CkABEoiS 3SoZcY+D3XPqAuM28fXDi6vnsPUo5B6jihRdYHCiub1CplK9nYmsk75ijBwSF0o4EExc iAZp+Tll4PT8lARkhlUcN9rlsC9437TYkXikFdQkS1ZsfbJ4uR6fZcs5XIvS/hmpik+0 UVjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692679931; x=1693284731; 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=FNvGqniYSJ51QuMFs79RM9uWOUFIvqo2X339VZOfyME=; b=MJL3YTe9pda0j2cALWz6GzQ2ihuHGTcgimipEEGaJHnHsQZpK3xZRFgmp0YEuVR1CP PyzXamHHUuh67GQ8VhdaK2OsBwq86g4AFk481aG6u4zAEag4rlR4L+6J1SWvH1+rXUBk HQjYajNFCv92QV4iTIPdN7g5cKqrO9m/3m7pPcpiGY8JmEUtp2HKXZZ2tdw16g7k90FV tQ1tC58TKk6ULkIfFtMfGhVh74L4sh2DwwRdUHoWFxiyWvshUFNt+w+QuQjLYsNfzkZz bM0RmQt3LkqsJgqEjx/HPeIECjFV40h4SaBQ4Ku/WoBKIpaF0Cx9RBiRmkO++hLVAOsj KWFw== X-Gm-Message-State: AOJu0YxfWEggdv1KWCRQDwORye6XFyiA868r5u8UU99LP97cjGj+IvEk +rCFZfp+kqaSDF6uUzevTUVomlvFkhw= X-Google-Smtp-Source: AGHT+IE6hcoShsUb5S3FBqnsWYyFIC4viHtAyon4eDqsnrXAANL5TmrR46Hvsc82IiO6ZZz+pOzKUA== X-Received: by 2002:a0d:f9c7:0:b0:573:7f55:a40e with SMTP id j190-20020a0df9c7000000b005737f55a40emr8676484ywf.49.1692679931376; Mon, 21 Aug 2023 21:52:11 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:6806:eeb6:3a6:c040? ([2600:1700:bd2c:b810:6806:eeb6:3a6:c040]) by smtp.googlemail.com with ESMTPSA id p5-20020a0dcd05000000b00589a1dc0809sm2616133ywd.120.2023.08.21.21.52.10 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Aug 2023 21:52:10 -0700 (PDT) Message-ID: Date: Mon, 21 Aug 2023 23:52:10 -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/21/23 18:49, Bruce Momjian wrote: > On Mon, Aug 21, 2023 at 07:02:46PM +0300, Mostafa Fathy wrote: >> Hi there, >> >> 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. -- Born in Arizona, moved to Babylonia.