From: Stephen Frost <sfrost@snowman.net>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Ants Aasma <ants.aasma@eesti.ee>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: WIP: Data at rest encryption
Date: Wed, 14 Jun 2017 17:41:19 -0400
Message-ID: <20170614214119.GL1769@tamriel.snowman.net> (raw)
In-Reply-To: <9cea5160-c64b-0b9e-d4b7-c57db2a696be@2ndquadrant.com>
References: <20170613172459.GL3151@tamriel.snowman.net>
<20170613174329.GK13873@momjian.us>
<20170613182339.GP3151@tamriel.snowman.net>
<20170613182910.GN13873@momjian.us>
<20170613183858.GR3151@tamriel.snowman.net>
<20170613185622.GO13873@momjian.us>
<20170613192011.GS3151@tamriel.snowman.net>
<a2fa2930-5334-c926-01ee-4a01c605b7a4@2ndquadrant.com>
<20170613221104.GT3151@tamriel.snowman.net>
<9cea5160-c64b-0b9e-d4b7-c57db2a696be@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Peter,
* Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
> 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.
I don't believe that was ever intended to be the final solution, I was
just pointing out that it's what the WIP patch did.
The discussion had moved into having a command called which provided the
key on stdout, as I recall, allowing it to be whatever the user wished,
including binary of any kind.
If you have other suggestions, I'm sure they would be well received. As
to the question of complexity, it certainly looks like it'll probably be
quite straight-forward for users to use.
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: sfrost@snowman.net, peter.eisentraut@2ndquadrant.com, bruce@momjian.us, ants.aasma@eesti.ee, robertmhaas@gmail.com
Subject: Re: WIP: Data at rest encryption
In-Reply-To: <20170614214119.GL1769@tamriel.snowman.net>
* 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