I use duplicity to create symmetrically encrypted backups to some server space I get from my ISP. When creating the backups I of course set a password and when I want to restore my files, duplicity asks for that password.
What I don't understand is that when I want to see which files are backed up and I run
duplicity list-current-files ftp://user@host/BACKUP
duplicity doesn't ask for the password, but just gives my the file list.
However, when I look at the files that are in that remote location, they all end in
.gpg and thus seem to be encrypted. When I download one of those files and want to open them with
tar tvf it fails. I can however decrypt the file with gpg and then look at it with tar.
duplicity list-current-files ask for the password? Couldn't this be considered a weakness?
I did some more testing and it seems that duplicity asks me for the password only the first time I try to
I downloaded the archive/backup files created by duplicity on the remote server to my local machine. When I ran
duplicity list-current-files file:///path/to/directory, it asked for the password. When I ran the command again, it didn't ask.
When restoring the files duplicity always asks for the password.
I did the same with a newly created (local) backup and the result was the same.