| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: XTS cipher mode for cluster file encryption |
| Date: | 2021-10-15 21:02:38 |
| Message-ID: | CA+TgmoYJMAtGSR3ragOrwrAiWhd_TA2mqMjBmMNOiHOA8pJv8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 15, 2021 at 3:22 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Specifically: The default cipher for LUKS is nowadays aes-xts-plain64
>
> and then this:
>
> https://gitlab.com/cryptsetup/cryptsetup/-/wikis/DMCrypt
>
> where plain64 is defined as:
>
> plain64: the initial vector is the 64-bit little-endian version of the
> sector number, padded with zeros if necessary
>
> That is, the default for LUKS is AES, XTS, with a simple IV. That
> strikes me as a pretty ringing endorsement.
Yes, that sounds promising. It might not hurt to check for other
precedents as well, but that seems like a pretty good one.
I'm not very convinced that using the LSN for any of this is a good
idea. Something that changes most of the time but not all the time
seems more like it could hurt by masking fuzzy thinking more than it
helps anything.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-10-15 21:21:09 | Re: XTS cipher mode for cluster file encryption |
| Previous Message | Tomas Vondra | 2021-10-15 20:57:03 | Re: XTS cipher mode for cluster file encryption |