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 1pDzr7-0000ae-Ny for pgsql-general@arkaria.postgresql.org; Sat, 07 Jan 2023 03:26:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pDzr4-0007hX-JL for pgsql-general@arkaria.postgresql.org; Sat, 07 Jan 2023 03:26:46 +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 1pDzr4-0007hO-9i for pgsql-general@lists.postgresql.org; Sat, 07 Jan 2023 03:26:46 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pDzr0-00040e-R5 for pgsql-general@lists.postgresql.org; Sat, 07 Jan 2023 03:26:45 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1pDzqq-00FCzl-8g; Fri, 06 Jan 2023 22:26:32 -0500 Date: Fri, 6 Jan 2023 22:26:32 -0500 From: Bruce Momjian To: Rainer Duffner Cc: "Peter J. Holzer" , pgsql-general@lists.postgresql.org Subject: Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration Message-ID: References: <285552b7273f57396398e5f7c538c7c4be60dce7.camel@cybertec.at> <69C40063-CF22-44FE-958A-74845CFBB039@ultra-secure.de> <8a66ead5-5463-11ed-e3d8-4d5962f81c36@gmail.com> <807557F0-F4F0-496A-B4B6-B043F8408A5B@ultra-secure.de> <20221222094622.y26t5reutijwnlop@hjp.at> <08F69776-6702-41F4-ACA5-CABF74CFE115@ultra-secure.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <08F69776-6702-41F4-ACA5-CABF74CFE115@ultra-secure.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Dec 22, 2022 at 11:15:57AM +0100, Rainer Duffner wrote: > I wasn’t involved in setting it up here, but AFAIK you need to „enroll“ the > client to the HSM. > > That is a one-time process that requires HSM credentials (via certificates and > pass-phrases). > > Then, that client can talk to the HSM. > > The HSM-client is (or should be) engineered in such a way that you can’t > extract the encryption-secret easily. > > I am not sure, but IIRC, you should not even be able to clone the VM without > the HSM noticing or the clone not working at all to begin with (for lack of > enrollment). Though most production databases are too large to just „clone“. > > Maybe someone who knows more about this subject can chime in before I make a > fool of myself? This wiki should help: https://wiki.postgresql.org/wiki/Transparent_Data_Encryption Also, the first two patches in this email are doc patches which explain the benefits: https://www.postgresql.org/message-id/20210625212204.GA7256@momjian.us -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Embrace your flaws. They make you human, rather than perfect, which you will never be.