From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Ants Aasma <ants.aasma@gmail.com>
To: Haribabu Kommi <kommi.haribabu@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: WIP: Data at rest encryption
Date: Mon, 13 Jun 2016 11:18:12 -0400
Message-ID: <29bd8421-d9f5-15fa-48b0-9ebc39ba8f94@2ndquadrant.com> (raw)
In-Reply-To: <CA+CSw_u1TPjWA66CvmAHgkSxQmpVHXOQNwXXMMBQQDp+FCxK2A@mail.gmail.com>
References: <CA+CSw_tb3bk5i7if6inZFc3yyf+9HEVNTy51QFBoeUk7UE_V=w@mail.gmail.com>
<CAJrrPGcPyMwtivJxKfjZLpSsnfgMsAvU0A7XDCsn7YYV-iJ2kQ@mail.gmail.com>
<CA+CSw_u1TPjWA66CvmAHgkSxQmpVHXOQNwXXMMBQQDp+FCxK2A@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 6/12/16 3:13 AM, Ants Aasma wrote:
>> 5. Instead of providing passphrase through environmental variable,
>> > better to provide some options to pg_ctl etc.
> That looks like it would be worse from a security perspective.
> Integrating a passphrase prompt would be an option, but a way for
> scripts to provide passphrases would still be needed.
Environment variables and command-line options are visible to other
processes on the machine, so neither of these approaches is really going
to work. We would need some kind of integration with secure
password-entry mechanisms, such as pinentry.
Also note that all tools that work directly on the data directory would
need password-entry and encryption/decryption support, including
pg_basebackup, pg_controldata, pg_ctl, pg_receivexlog, pg_resetxlog,
pg_rewind, pg_upgrade, pg_xlogdump.
It seems that your implementation doesn't encrypt pg_control, thus
avoiding some of that. But that doesn't seem right.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: peter.eisentraut@2ndquadrant.com, ants.aasma@gmail.com, kommi.haribabu@gmail.com
Subject: Re: WIP: Data at rest encryption
In-Reply-To: <29bd8421-d9f5-15fa-48b0-9ebc39ba8f94@2ndquadrant.com>
* 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