Postgres Pro
Downloads
Home   >   mailing lists

Re: storing an explicit nonce - Mailing list pgsql-hackers

From Sasasu
Subject Re: storing an explicit nonce
Date
Msg-id e8d8be0f-d3d2-a3e7-8dc1-79b16c3ae3ca@sasa.su
Whole thread Raw
In response to Re: storing an explicit nonce  (Sasasu <i@sasa.su>)
List pgsql-hackers
Tree view 

在 2021/9/5 下午10:51, Sasasu 写道:
>
> For AES-GCM, a predictable IV is fine. I think we can decrypt and
> re-encrypt the user data in pg_upgrade. this will allows us to use
> relfile oid + block number as nonce.

relfile oid + block number + some counter for heap table IV. I mean.
Attachment

pgsql-hackers by date:

Previous
From: "kuroda.hayato@fujitsu.com"
Date:
Subject: RE: Allow escape in application_name (was: [postgres_fdw] add local pid to fallback_application_name)
Next
From: Masahiro Ikeda
Date:
Subject: Re: Allow escape in application_name