pg.ddx.io pgsql-general@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Rainer Duffner <rainer@ultra-secure.de>
To: Peter J. Holzer <hjp-pgsql@hjp.at>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration
Date: Thu, 22 Dec 2022 11:15:57 +0100
Message-ID: <08F69776-6702-41F4-ACA5-CABF74CFE115@ultra-secure.de> (raw)
In-Reply-To: <20221222094622.y26t5reutijwnlop@hjp.at>
References: <MAXPR01MB2688CFCA349F11FAD7B495EB9EEB9@MAXPR01MB2688.INDPRD01.PROD.OUTLOOK.COM>
<285552b7273f57396398e5f7c538c7c4be60dce7.camel@cybertec.at>
<69C40063-CF22-44FE-958A-74845CFBB039@ultra-secure.de>
<CAD+mzowEcJ9==68MkZd7vFUVHuJPGQsrx=ztQp7Sp1T5M0TeoQ@mail.gmail.com>
<8a66ead5-5463-11ed-e3d8-4d5962f81c36@gmail.com>
<CAD+mzox3w32krF4Xz=maowYPe3-V2N0DABKu=obvHUQL9CaZSQ@mail.gmail.com>
<807557F0-F4F0-496A-B4B6-B043F8408A5B@ultra-secure.de>
<20221222094622.y26t5reutijwnlop@hjp.at>
> Am 22.12.2022 um 10:46 schrieb Peter J. Holzer <hjp-pgsql@hjp.at>:
>
> If the hacker has root access: What prevents them from talking to the
> HSM?
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?
;-)
Rainer=
view thread (14+ messages) latest in thread
Message-ID: <08F69776-6702-41F4-ACA5-CABF74CFE115@ultra-secure.de> Permalink: ../08F69776-6702-41F4-ACA5-CABF74CFE115@ultra-secure.de/ Also on: postgresql.org/message-id/08F69776-6702-41F4-ACA5-CABF74CFE115@ultra-secure.de ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-general@postgresql.org Cc: rainer@ultra-secure.de, hjp-pgsql@hjp.at Subject: Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration In-Reply-To: <08F69776-6702-41F4-ACA5-CABF74CFE115@ultra-secure.de> References: <MAXPR01MB2688CFCA349F11FAD7B495EB9EEB9@MAXPR01MB2688.INDPRD01.PROD.OUTLOOK.COM> <285552b7273f57396398e5f7c538c7c4be60dce7.camel@cybertec.at> <69C40063-CF22-44FE-958A-74845CFBB039@ultra-secure.de> <CAD+mzowEcJ9==68MkZd7vFUVHuJPGQsrx=ztQp7Sp1T5M0TeoQ@mail.gmail.com> <8a66ead5-5463-11ed-e3d8-4d5962f81c36@gmail.com> <CAD+mzox3w32krF4Xz=maowYPe3-V2N0DABKu=obvHUQL9CaZSQ@mail.gmail.com> <807557F0-F4F0-496A-B4B6-B043F8408A5B@ultra-secure.de> <20221222094622.y26t5reutijwnlop@hjp.at> <08F69776-6702-41F4-ACA5-CABF74CFE115@ultra-secure.de> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox