On Fri, Jun 5, 2020 at 03:34:54PM +0200, Fabien COELHO wrote: > Obviously it requires some more thinking and design, but my point is that > postgres should not hold a KEK, ever, nor presume how DEK are to be managed > by a DMS, and that is not very difficult to achieve by putting it outside of > pg and defining how interactions take place. Providing a reference/example > implementation would be nice as well, and Masahiko-san code can be rewrapped > quite easily.
Well, the decrypted keys are already stored in backend memory, so what risk does haveing the KEK in memory for a brief period avoid? -- Bruce Momjian <br...@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
