4 ms·
What exactly do you mean with encrypted replication? Just stream the WAL in an encrypted format, and store it there? Easy enough. But that'll mean that it'll p
by anarazel 10y ago
What exactly do you mean with encrypted replication?
Just stream the WAL in an encrypted format, and store it there? Easy enough. But that'll mean that it'll potentially take a long time to re-apply all those changes to a base backup.
Actually apply the changes, even though the database and WAL in encrypted? Unlikely, don't really see how that'd be possible. And even if, I'd bet that it'd be fairly easy to generate compression type attacks.
- JoshTriplett 10y agoYou'd need some sort of encryption of the raw data storage, and that would also prevent backing up any indexes. And yes, you'd expose some amount of information, such as row activity. Seems plausible, though, depending on your threat model.
- anarazel 10y agoIf I were to do that I'd use logical decoding (https://www.postgresql.org/docs/current/static/logicaldecoding.html https://www.postgresql.org/docs/current/static/logicaldecodi...) and just write a custom apply mechanism. I think you'll, in any case, end up exposing a lot of information. INSERT/UPDATE/DELETE are going to be discernible, and you'd have to be very careful about compression not exposing things. The backup wouldn't actually be particularly useful though. So I'm not really sure what the use-case here is.