Created
June 12, 2012 04:11
-
-
Save kuleszaj/2914866 to your computer and use it in GitHub Desktop.
Duplicity: asymmetric encryption and signing with GnuPG
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Duplicity: asymmetric encryption and signing with GnuPG, using the given keys to encrypt and sign the backups | |
| # --encrypt-key : The ID of the GPG key you will be using to encrypt the data | |
| # --sign-key : The ID of the GPG key you will be using to sign the backup files | |
| # The encrypt-key needs to already be signed by the sign-key. Both keys need to be appropriately trusted. | |
| # --full-if-older-than 30D : If a full backup hasn't been made in the last 30 days, create a new backup set starting with a full backup | |
| # --volsize 250 : Create volumes with a size of 250 MB | |
| # /current_backups/mysecurefiles : The directory to encrypt and backup. | |
| # s3+http://my-backups/mysecurefiles : The Amazon S3 container ('my-backups') and directory ('mystuff') to place the encrypted backups in. | |
| export AWS_ACCESS_KEY_ID=your_aws_access_key_id | |
| export AWS_SECRET_ACCESS_KEY=your_aws_secret_access_key | |
| export PASSPHRASE=secretsigningpassphrase | |
| duplicity --encrypt-key "<encrypt-key-id>" --sign-key "<sign-key-id>" --full-if-older-than 30D --volsize 250 /current_backups/mysecurefiles s3+http://my-backups/mystuff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment