mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 05:35:57 +03:00
[GH-ISSUE #6] Backups Not Encrypted #5
Labels
No labels
bug
confirmed next step
duplicate
enhancement
help wanted
in progress
in progress
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pgbackweb#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nealhead on GitHub (Jul 30, 2024).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/6
It would appear that the backups in the S3 bucket are stored in an unencrypted ZIP file. Is this intended?
@eduardolat commented on GitHub (Jul 30, 2024):
Yes, that's how it works.
PG Back Web encrypts sensitive data (connection strings, keys, etc.) stored in its own database.
Regarding storage, data is encrypted by default on the majority of S3 storage providers, so the responsibility is delegated to them.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingEncryption.html
https://www.backblaze.com/docs/cloud-storage-server-side-encryption
https://docs.wasabi.com/docs/how-secure-is-my-data-1
https://developers.cloudflare.com/r2/reference/data-security/
https://www.digitalocean.com/security/shared-responsibility-model-spaces
@eduardolat commented on GitHub (Jul 30, 2024):
Maybe in the future when other features on the to-do list are done we can add a flag to add an encryption layer by PG Back Web