Date: Wed, 14 Jun 2017 16:13:57 +0300
From: Aleksander Alekseev <a.alekseev@postgrespro.ru>
To: Kenneth Marshall <ktm@rice.edu>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
	Ants Aasma <ants.aasma@eesti.ee>,
	Robert Haas <robertmhaas@gmail.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: WIP: Data at rest encryption
Message-ID: <20170614131357.GC11767@e733.localdomain>
References: 
 <CA+CSw_tb3bk5i7if6inZFc3yyf+9HEVNTy51QFBoeUk7UE_V=w@mail.gmail.com>
 <06b6db11-3a3f-4d24-6f57-450f96ecda84@2ndquadrant.com>
 <CA+TgmoaXGx=7VEVz7eq9T=raZRHm3iNc244Sx=T1UxX-+szOUQ@mail.gmail.com>
 <CA+CSw_uO6wGv2YF-RQvVOGeezJXWY+SGTKYomOY=fDNp6OmHqA@mail.gmail.com>
 <babf2042-3a7f-1601-7767-b34707194462@2ndquadrant.com>
 <20170614090426.GA7249@e733.localdomain>
 <20170614124601.GM26506@aart.rice.edu>
 <20170614130509.GB11767@e733.localdomain>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="p2kqVDKq5asng8Dg"
Content-Disposition: inline
In-Reply-To: <20170614130509.GB11767@e733.localdomain>
User-Agent: Mutt/1.8.3 (2017-05-23)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


--p2kqVDKq5asng8Dg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> > 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.
>=20
> Frankly I'm having difficulties imagining when it could be a real
> problem. It doesn't seem to be such a burden to ask a colleague for
> assistance in case you don't have sufficient permissions to do
> something. And I got a strong feeling that solving bureaucracy issues of
> specific organizations by changing PostgreSQL core in very invasive way
> (keeping in mind testing, maintaining, etc) is misguided.

In the same time implementing a plugable storage API and then implementing
encrypted / compressed / whatever storage in a standalone extension using
this API seems to be a reasonable thing to do.=20

--=20
Best regards,
Aleksander Alekseev

--p2kqVDKq5asng8Dg
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEECAokn0QZCoIHW4GpEEnCBLXCDtYFAllBNpUACgkQEEnCBLXC
DtYPOQ//UOTkOSoXhKVcFxNwFbbp4HLuBKTSsbS09Tbt1t4dLnHEO0HFmOq+UnKJ
rb9178LKqOtekySs4sZi7hiD7KkUoJt25fQrnIbsSjIkSlasN1JFOjImRI5rWr+m
LMVzccPUOj3sfLWyQJJpPzKh/Zrs4wLIZqeDVwgBb2N7tT1xfUTtYvJ13PD+kzC4
uygtWIYRFZb44eGo6qDAYR+mG7MV2TmPyzwZ9FsSIL2atKTRUlXzEU+vEOHXSVZA
+jhz468bQRNBiHK4ESL6yM01YqDTq78eyvu3nzm0B5/yDgASc/GXN9fGqWmSf0LY
bSa2CwpMpn9NqQ7oBOOvpfdIPjWBZinaVOre2Vs8Gf/gs0ympVAQOUFoHEY1M7+L
ADy148P3mG7ETkSKIJsN4bRaT2PODkyby9pplNx9riMXhfXkno+dc9i2bQ0P5Np6
w/ylnW6CwqWZ1tuX2y0mSh2YMfveziNlal7mhZ5FWpVTI9OUbWgA4FtHiB6UwEbY
f9r+B1HT83fzMaYofMV85qrYD02GJyKi9NamPk4ECoFV31DIRiks0obBbaKbfz1g
znS3KyDNvkOsgjCsWdMWrekBPQLVmw/yhaVf9bHvLwY0Bzvt6FYN/iHhXZB+gxbZ
y9irL+1rMJwErG2A2eEeELQi2mcIsO5Fqa+05pOFe42fMru64/A=
=Fh8f
-----END PGP SIGNATURE-----

--p2kqVDKq5asng8Dg--