Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Sehrope Sarkuni <sehrope@jackdb.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, Joe Conway <mail@joeconway.com>, Antonin Houska <ah@cybertec.at>, Stephen Frost <sfrost@snowman.net>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Haribabu Kommi <kommi.haribabu@gmail.com>, "Moon, Insung" <Moon_Insung_i3@lab.ntt.co.jp>, Ibrar Ahmed <ibrar.ahmad@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-08-13T00:14:32Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Revamp the WAL record format.
- 2c03216d8311 9.5.0 cited
On Sat, Aug 10, 2019 at 08:06:17AM -0400, Bruce Momjian wrote: > So, I just had an indea if we use separate encryption keys for > heap/index and for WAL --- we already know we will have an offline tool > that can rotate the passphrase or encryption keys. If we allow the > encryption keys to be rotated independently, we can create a standby, > and immediately rotate its heap/index encryption key. We can then start > streaming replication. When we promote the standby to primary, we can > then shut it down and rotate the WAL encryption key --- the new primary > would then have no shared keys with the old primary. To help move this forward, I created a new wiki TDE section titled "TODO for Full-Cluster Encryption" and marked some unresolved items with question marks: https://wiki.postgresql.org/wiki/Transparent_Data_Encryption#TODO_for_Full-Cluster_Encryption I have also updated some of the other text to match conclusions we have made. I know some of the items are done, but if we have agreement on moving forward, I can help with some of the missing code. This looks doable for PG 13 if we start soon. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +