The history file is definitely not encrypted. According to S3, the 00000009.history.lzo file has not been modified since March. I do have wal segments in that same bucket/directory that are definitely encrypted though.
On Wednesday, July 27, 2016 at 12:50:22 PM UTC-5, Daniel Farina wrote: > > On Wed, Jul 27, 2016 at 9:44 AM <[email protected] <javascript:>> wrote: > >> I'm currently working on adding gpg encryption to my existing wal-e >> backups. I've got it 90% working, everything is using the GPG key via env >> variable, and backup-push and backup-fetch seem to be working fine. >> >> As part of my last bit of testing, I set up a new replica, and had it >> restore via backup-fetch. However, the new replica is trying to set up >> replication, and failing on wal-fetch. >> It seems wal-e is trying to use the history files, but at this point they >> are not gpg encrypted, and I'm not sure where to go from here. >> > > That seems like a bug. Have you confirmed the contents are unencrypted? > > Probably for uniformity sake the history file should be encrypted. > -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
