Re: storing an explicit nonce
От | vignesh C |
---|---|
Тема | Re: storing an explicit nonce |
Дата | |
Msg-id | CALDaNm00sWfWK8HFVf9HbJ1Xz_Q9Eef8-ZojnnmsA+rxUKe0rA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: storing an explicit nonce (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: storing an explicit nonce
|
Список | pgsql-hackers |
On Sat, Jun 26, 2021 at 2:52 AM Bruce Momjian <bruce@momjian.us> wrote: > > On Wed, May 26, 2021 at 05:02:01PM -0400, Bruce Momjian wrote: > > For these reasons, if we decide to go in the direction of using a > > non-LSN nonce, I no longer plan to continue working on this feature. I > > would rather work on things that have a more positive impact. Maybe a > > non-LSN nonce is a better long-term plan, but there are too many > > unknowns and complexity for me to feel comfortable with it. > > As stated above, I have no plans to continue working on this feature. I > am attaching my final patches here in case anyone wants to make use of > them; it passes check-world and all my private tests. I have removed > my patches from the feature wiki page: > > https://wiki.postgresql.org/wiki/Transparent_Data_Encryption > > and replaced it with a link to this email. The patch does not apply on Head anymore, could you rebase and post a patch. I'm changing the status to "Waiting for Author". Regards, Vignesh
В списке pgsql-hackers по дате отправления: