| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Antonin Houska <ah(at)cybertec(dot)at>, Toshi Harada <harada(dot)toshi(at)po(dot)ntt-tx(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3 |
| Date: | 2019-03-15 21:48:24 |
| Message-ID: | CA+TgmoZ6x-2NNav8f2iAWYhj13dTUZOJW7GAvhz5t0wzSCcb2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 15, 2019 at 5:10 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> ISTM that this is only a problem if you choose the wrong encryption
> method. One not-wrong encryption method is to use a stream cipher
> --- maybe that's not the exact right technical term, but anyway
> I'm talking about a method which notionally XOR's the cleartext
> data with a random bit stream generated from the encryption key
> (probably along with other knowable inputs such as the block number).
> In such a method, corruption of individual on-disk bytes doesn't
> prevent you from getting the correct decryption of on-disk bytes
> that aren't corrupted.
Oh, that seems like it might be a really good idea.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yun Li | 2019-03-15 21:54:19 | Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |
| Previous Message | Robert Haas | 2019-03-15 21:41:47 | Re: hyrax vs. RelationBuildPartitionDesc |