Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dL7i3-0007By-00 for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Jun 2017 12:47:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dL7i1-0007yu-RC for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Jun 2017 12:47:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dL7gV-0005HU-VM for pgsql-hackers@postgresql.org; Wed, 14 Jun 2017 12:46:08 +0000 Received: from aart.rice.edu ([168.7.56.48]) by magus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dL7gR-0005hS-LN for pgsql-hackers@postgresql.org; Wed, 14 Jun 2017 12:46:07 +0000 Received: by aart.rice.edu (Postfix, from userid 18612) id B02AA4069687; Wed, 14 Jun 2017 07:46:01 -0500 (CDT) Date: Wed, 14 Jun 2017 07:46:01 -0500 From: Kenneth Marshall To: Aleksander Alekseev Cc: Peter Eisentraut , Ants Aasma , Robert Haas , PostgreSQL-development Subject: Re: WIP: Data at rest encryption Message-ID: <20170614124601.GM26506@aart.rice.edu> References: <06b6db11-3a3f-4d24-6f57-450f96ecda84@2ndquadrant.com> <20170614090426.GA7249@e733.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170614090426.GA7249@e733.localdomain> User-Agent: Mutt/1.5.21 (2010-09-15) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On Wed, Jun 14, 2017 at 12:04:26PM +0300, Aleksander Alekseev wrote: > Hi Ants, > > On Tue, Jun 13, 2017 at 09:07:49AM -0400, Peter Eisentraut wrote: > > On 6/12/17 17:11, Ants Aasma wrote: > > > I'm curious if the community thinks this is a feature worth having? > > > Even considering that security experts would classify this kind of > > > encryption as a checkbox feature. > > > > File system encryption already exists and is well-tested. I don't see > > any big advantages in re-implementing all of this one level up. You > > would have to touch every single place in PostgreSQL backend and tool > > code where a file is being read or written. Yikes. > > I appreciate your work, but unfortunately I must agree with Peter. > > On Linux you can configure the full disc encryption using LUKS / > dm-crypt in like 5 minutes [1]. On FreeBSD you can do the same using > geli [2]. In my personal opinion PostgreSQL is already complicated > enough. A few companies that hired system administrators that are too > lazy to read two or three man pages is not a reason to re-implement file > system encryption (or compression, or mirroring if that matters) in any > open source RDBMS. > Hi Aleksander, While I agree that configuring full disk encryption is not technically difficult, it requires much more privileged access to the system and basically requires the support of a system administrator. In addition, if a volume is not available for encryption, PostgreSQL support for encryption would still allow for its data to be encrypted and as others have mentioned can be enabled by the DBA alone. Regards, Ken -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers