On 6/16/19 9:46 AM, Bruce Momjian wrote: > On Sun, Jun 16, 2019 at 09:45:09AM -0400, Bruce Momjian wrote: >> On Sun, Jun 16, 2019 at 07:07:20AM -0400, Joe Conway wrote: >> > And although I'm not proposing this for the first implementation, yet >> > another reason is I might want to additionally control "transparent >> > access" to data based on who is logged in. That could be done by >> > layering an additional key on top of the per-tablespace key for example. >> > >> > The bottom line in my mind is encrypting the entire database with a >> > single key is not much different/better than using filesystem >> > encryption, so I'm not sure it is worth the effort and complexity to get >> > that capability. I think having the ability to encrypt at the tablespace >> > level adds a lot of capability for minimal extra complexity. >> >> I disagree. > > I will add that OpenSSL has been removing features and compatibility > because the added complexity had hidden exploits that they could not > have anticipated.
Sorry but I'm not buying it. Joe -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
signature.asc
Description: OpenPGP digital signature
