Re: storing an explicit nonce

On Tue, Oct 5, 2021 at 04:29:25PM -0400, Bruce Momjian wrote:
> On Tue, Sep 28, 2021 at 12:30:02PM +0300, Ants Aasma wrote:
> > On Mon, 27 Sept 2021 at 23:34, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > We are still working on our TDE patch. Right now the focus is on refactoring
> > temporary file access to make the TDE patch itself smaller. Reconsidering
> > encryption mode choices given concerns expressed is next. Currently a viable
> > option seems to be AES-XTS with LSN added into the IV. XTS doesn't have an
> > issue with predictable IV and isn't totally broken in case of IV reuse.
>
> Uh, yes, AES-XTS has benefits, but since it is a block cipher, previous
> 16-byte blocks affect later blocks, meaning that hint bit changes would
> also affect later blocks. I think this means we would need to write WAL
> full page images for hint bit changes to avoid torn pages. Right now
> hint bit (single bit) changes can be lost without causing torn pages.
> This was another of the advantages of using a stream cipher like CTR.

The above text isn't very clear. What I am saying is that currently
torn pages can be tolerated by hint bit writes because only a single
byte is changing. If we use a block cipher like AES-XTS, later 16-byte
encrypted blocks would be changed by hint bit changes, meaning torn
pages could not be tolerated. This means we would have to use full page
writes for hint bit changes, perhaps making this feature have
unacceptable performance overhead.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.