| From: | Ants Aasma <ants(at)cybertec(dot)at> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Antonin Houska <ah(at)cybertec(dot)at>, Robert Haas <robertmhaas(at)gmail(dot)com>, Sasasu <i(at)sasa(dot)su>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: storing an explicit nonce |
| Date: | 2021-10-12 21:48:51 |
| Message-ID: | CANwKhkM+sRgtxB4E9ssdujnBdLL_6_Z_V-+Gg9bGDyNq7X8zPQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 13 Oct 2021 at 00:25, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Tue, Oct 12, 2021 at 11:21:28PM +0300, Ants Aasma wrote:
> > On Tue, 12 Oct 2021 at 16:14, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > Well, how do you detect an all-zero page vs a page that encrypted to
> all
> > zeros?
> >
> > Page encrypting to all zeros is for all practical purposes impossible to
> hit.
> > Basically an attacker would have to be able to arbitrarily set the whole
> > contents of the page and they would then achieve that this page gets
> ignored.
>
> Uh, how do we know that valid data can't produce an encrypted all-zero
> page?
>
Because the chances of that happening by accident are equivalent to making
a series of commits to postgres and ending up with the same git commit hash
400 times in a row.
--
Ants Aasma
Senior Database Engineerwww.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-10-12 21:53:01 | Re: storing an explicit nonce |
| Previous Message | Bruce Momjian | 2021-10-12 21:25:48 | Re: storing an explicit nonce |