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: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: 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-07-25T17:23:40Z
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 Thu, Jul 25, 2019 at 01:18:44PM -0400, Bruce Momjian wrote: > > Key Management > > ============== > > We will use 3-tier key architecture as Joe proposed. > > > > 1. A master key encryption key (KEK): this is the ley supplied by the > > database admin using something akin to ssl_passphrase_command > > > > 2. A master data encryption key (MDEK): this is a generated key using a > > cryptographically secure pseudo-random number generator. It is > > encrypted using the KEK, probably with Key Wrap (KW): > > or maybe better Key Wrap with Padding (KWP): > > > > 3a. Per table data encryption keys (TDEK): use MDEK and HKDF to generate > > table specific keys. > > What is the value of a per-table encryption key? How is HKDF derived? > Are we still unclear if the 68GB limit is per encryption key or per > encryption key/IV combination? Oh, I see you got this from Joe Conway's email. Let me reply to that now. (I am obviously having problems keeping this thread in my head as well.) -- 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 +