| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Antonin Houska <ah(at)cybertec(dot)at>, Bruce Momjian <bruce(at)momjian(dot)us>, Toshi Harada <harada(dot)toshi(at)po(dot)ntt-tx(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3 |
| Date: | 2019-06-26 13:05:52 |
| Message-ID: | b1733b72-0102-2d5f-15c2-852bc879bdf0@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-06-25 15:39, Robert Haas wrote:
> On Tue, Jun 25, 2019 at 8:28 AM Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> How are the requirements here different from ssl_passphrase_command?
>> Why do we need a new mechanism?
>
> I don't think that the requirements are different, and I don't think
> we need a new mechanism.
>
> I am curious exactly how you would set up ssl_passphrase_command to
> prompt interactively.
For example like this:
https://www.2ndquadrant.com/en/blog/postgresql-passphrase-protected-ssl-keys-systemd/
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-26 13:40:30 | Re: mcvstats serialization code is still shy of a load |
| Previous Message | Andrew Gierth | 2019-06-26 13:01:43 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |