Re: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Antonin Houska <ah@cybertec.at>, Robert Haas <robertmhaas@gmail.com>, Toshi Harada <harada.toshi@po.ntt-tx.co.jp>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2019-07-06T02:33:07Z
Lists: pgsql-hackers
On Tue, Jun 25, 2019 at 02:28:00PM +0200, Peter Eisentraut wrote: > On 2019-06-17 11:23, Antonin Houska wrote: > > I'm thinking how to teach postmaster to accept FEBE protocol connections > > temporarily, just to receive the key. The user applications like pg_ctl, > > initdb or pg_upgrade would retrieve the key / password from the DBA, then > > start postmaster and send it the key. > > > > Perhaps the message format should be a bit generic so that extensions like > > this can use it to receive their keys too. > > > > (The idea of an unix socket or named pipe I proposed upthread is not good > > because it's harder to implement in a portable way.) > > How are the requirements here different from ssl_passphrase_command? > Why do we need a new mechanism? Agreed. My pgcryptokey prompting shell script was mostly a proof-of-concept. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
Commits
-
Dramatically reduce System V shared memory consumption.
- b0fc0df9364d 9.3.0 cited