Introducing WAL-G: Faster Disaster Recovery for Postgres

Re:Introducing WAL-G: Faster Disaster Recovery for Postgres by fdr on Friday August 18, 2017 @05:01PM (#15049691)

Do you want GPG based or some other client side encryption, or S3's encryption support? The latter could probably just be turned on. The former is a feature requiring code.

[ Parent | on HN ]

Re:Introducing WAL-G: Faster Disaster Recovery for Postgres by upbeatlinux on Friday August 18, 2017 @06:51PM (#15050363)

Ideally the presence of the `WALE_GPG_KEY_ID` env var should enable encrypted backups https://github.com/wal-e/wal-e#encryption.

Put differently to be a "successor" it needs to be a drop in replacement ;)

[ Parent | on HN ]

Re:Introducing WAL-G: Faster Disaster Recovery for Postgres by trojanowski on Saturday August 19, 2017 @03:23AM (#15052157)

Alternatively you could use a combination of AES and RSA similar how pghoard implements it: https://github.com/ohmu/pghoard

The RSA keys (or path to them) would be passed as environment variables. It would be a little easier to setup than gpg (especially for automatic backup restoration).

[ Parent | on HN ]

Re:Introducing WAL-G: Faster Disaster Recovery for Postgres by fdr on Friday August 18, 2017 @07:48PM (#15050633)

I have to be selective about maintenance of features. I'll consider GPG support.

[ Parent | on HN ]

Re:Introducing WAL-G: Faster Disaster Recovery for Postgres by tatersolid on Sunday August 20, 2017 @10:31PM (#15061518)

Please consider libsodium or a similar "modern" crypto library instead. There's a lot of ugly 90s crypto in GPG and the API is terrible. Libsodium makes it hard for non-crypto devs to shoot themselves in the foot, and is much less code to write.

[ Parent | on HN ]