-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encrypt database backups #8
Comments
Standard zip encryption with PKZIP is unsafe. Firstly, a distinction must be made between symmetric or asymmetric encryption.
Considering that db:compress and db:decompress are both executed on the deployment target, asymmetric encryption is not totally useful here. Besides, database dumps can be large and encryption should be fast. Looking at symmetric encryption, AES-256 might be the best choice for two reasons:
When using encryption, there is more to consider:
The current openssl version on Debian 11 supports these ciphers:
aes-256-ctr seems to be a safe choice: https://crypto.stackexchange.com/questions/6029/aes-cbc-mode-or-aes-ctr-mode-recommended Base on the above research, we could use openssl like this:
Speed test on Cloud VM with 2 Cores @ 2GHz
Todos:
|
The database dumps created by deployer (
{{deploy_path}}/.dep/database/dumps
) are not encrypted and therefore a potentially security risk.It would be nice to extend the
db:compress
/db:decompress
commands for a password option of the gzip command.This feature could be used as a PR for deployer-extended-database
The text was updated successfully, but these errors were encountered: