Duplicity can often use a lot of disk space for temporary files and the archive cache. It's tempting to use the --archive-dir and --tempdir arguments in order to store these on the same disk where the backups are placed, but I can't find any information on whether these files can potentially expose unencrypted data.

From the man page:

The remote signatures will be encrypted if encryption is enabled. The local signatures will not be encrypted and stored in the archive dir (see --archive-dir ).

These clearly states that the signatures are not encrypted, but I'm not completely sure what information is stored in the signatures. My guess is that this includes filenames, sizes, permissions, and last modified times, but not any data from within files. Is that correct?

My bigger worry is that the temporary files are unencrypted archives which are then encrypted before being copied to the destination. I can't find any information about whether or not this is the case, and the codebase is complex enough that it wasn't easy to see exactly how the temporary files are used. Does anybody know if they are used to store unencrypted archives?


your assumption is correct. neither files in archive dir nor in temp folder can be assumed to be encrypted.

archive dir contains unencrypted usable copies of the remote metadata.

the temp folder is used to create data volumes and their encrypted pendants or used to download remote files and decrypt them.

in summary - don't place archive dir or temp folder on an untrusted device.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.