Re: storing an explicit nonce

Sasasu <i@sasa.su>

From: Sasasu <i@sasa.su>

To: pgsql-hackers@lists.postgresql.org

Date: 2021-09-06T02:04:33Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Rethink method for assigning OIDs to the template0 and postgres DBs.
- 2cb1272445d2 15.0 landed
pg_upgrade: Preserve database OIDs.
- aa01051418f1 15.0 landed
pg_upgrade: Preserve relfilenodes and tablespace OIDs.
- 9a974cbcba00 15.0 landed
Fix for new Boolean node
- cf925936ecc0 15.0 cited
Improve error handling of HMAC computations
- 5513dc6a304d 15.0 cited
Add macro RelationIsPermanent() to report relation permanence
- 95d77149c535 14.0 landed
Enhance nbtree index tuple deletion.
- d168b666823b 14.0 cited

Attachments

OpenPGP_0x4E72AF09097DAE2E.asc (application/pgp-keys)


在 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.