| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Data at rest encryption |
| Date: | 2017-06-14 21:36:16 |
| Message-ID: | 9cea5160-c64b-0b9e-d4b7-c57db2a696be@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/13/17 18:11, Stephen Frost wrote:
>> Let's see a proposal in those terms then. How easy can you make it,
>> compared to existing OS-level solutions, and will that justify the
>> maintenance overhead?
> From the original post on this thread, which included a WIP patch:
>
> ----------------------------------
> Usage
> =====
>
> Set up database like so:
>
> (read -sp "Postgres passphrase: " PGENCRYPTIONKEY; echo;
> export PGENCRYPTIONKEY
> initdb -k -K pgcrypto $PGDATA )
>
> Start PostgreSQL:
>
> (read -sp "Postgres passphrase: " PGENCRYPTIONKEY; echo;
> export PGENCRYPTIONKEY
> postgres $PGDATA )
> ----------------------------------
Relying on environment variables is clearly pretty crappy. So if that's
the proposal, then I think it needs to be better.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-06-14 21:41:19 | Re: WIP: Data at rest encryption |
| Previous Message | Peter Eisentraut | 2017-06-14 21:32:06 | Re: WIP: Data at rest encryption |