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 1p8Nxn-0000eB-79 for pgsql-general@arkaria.postgresql.org; Thu, 22 Dec 2022 15:58:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p8Nxm-0000hb-0d for pgsql-general@arkaria.postgresql.org; Thu, 22 Dec 2022 15:58:30 +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 1p8Nxl-0000hR-Mc for pgsql-general@lists.postgresql.org; Thu, 22 Dec 2022 15:58:29 +0000 Received: from mail.hjp.at ([212.17.106.138] helo=rorschach.hjp.at) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p8Nxh-0005o3-VP for pgsql-general@lists.postgresql.org; Thu, 22 Dec 2022 15:58:29 +0000 Received: by rorschach.hjp.at (Postfix, from userid 1000) id 5333A8BB3; Thu, 22 Dec 2022 16:58:24 +0100 (CET) Date: Thu, 22 Dec 2022 16:58:24 +0100 From: "Peter J. Holzer" To: pgsql-general@lists.postgresql.org Subject: Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration Message-ID: <20221222155824.db6yaqfmue5o7a4t@hjp.at> Mail-Followup-To: pgsql-general@lists.postgresql.org 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: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="l3mm5as6kbouwiok" Content-Disposition: inline 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 --l3mm5as6kbouwiok Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2022-12-22 11:15:57 +0100, Rainer Duffner wrote: >=20 >=20 > Am 22.12.2022 um 10:46 schrieb Peter J. Holzer : >=20 > If the hacker has root access: What prevents them from talking to the > HSM? >=20 >=20 >=20 > I wasn=E2=80=99t involved in setting it up here, but AFAIK you need to = =E2=80=9Eenroll=E2=80=9C the > client to the HSM. >=20 > That is a one-time process that requires HSM credentials (via certificate= s and > pass-phrases). >=20 > Then, that client can talk to the HSM.=20 Which means that some sort of access-token is stored on the client. So what prevents a hacker from using that access token? > The HSM-client is (or should be) engineered in such a way that you can=E2= =80=99t > extract the encryption-secret easily. Security by obscurity? Just hope that nobody figures out how that access token is stored? That doesn't seem like a good strategy against high-level threats. hp --=20 _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp@hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" --l3mm5as6kbouwiok Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmOkfpYACgkQ8g5IURL+ KF1CehAArM/NbNIZnipQw5C00NC9n9Brwv7HrWdUwSqESwO5yx92vVVBCMeL55FP Gb1emgDRom1vS0cOFALQreKzVt6E2cQwXjXcQ4fr9bRER7ueStcMVELZEqojkiVo dqw9zZ8AIWrprutC5IyDuLVDkqEp0yNTxvJpJKtcFVjcl9Gd4fyH7oQrd8HRHElY 792mSdlW073YE6hgkc+SHy9IC/ztwVHkSSkWosFvMTR/C34uHnaspo17TSvfQJM0 nZ7AXYZB4uAL+E0jBX1GWPqAHzgIQ8unF6iPhfb6Ad9L6ccxyGuGtDwoY2623WSY GY/aLmhLZT9u8z+A3kjVcgLr+Dil0RD10v25liFCVyGN7wqBikQFyNKjvTdk8l+i ymTPggl02cs+GjWCZv4G2Eac71BOlJpUqgGdHf4j1vcZrOX0Sy+mQOkc21j7ejwj 0Mw4pdRR/3F7Dcwc9n19fxwsZz6gory3BI2U2OPifqi6Fnb3ZOafPgzs1ZmOW3yp 8VQsKz0sUMGNhCsk1hb4mtG581NORAMqpEKhKUYDQJ7EiC9i+0M+IsW+l5bda9Cp q2VGpiuyDthPXqXci0sZ54I2+h2lVLcmq6a5037ZmRsCzRCmuhTmZwuRchPOOUpV nXCL8yL68UocA11ASemfFEm4NBGdbK31Fh+/hhiU0LWSIaZtv+c= =vno5 -----END PGP SIGNATURE----- --l3mm5as6kbouwiok--