I am trying to setup a backup server using duply and a secure connection. I have created the ~/.ssh/config file with the following content: Host backup IdentityFile ~/.ssh/id_ed25519_backup Hostname Port 22 User Furthermore, I have also defined the known_hosts file, by copy-pasting in it the server public key (found in /etc/ssh/ssh_host_ed25519_key.pub) All seems to work properly when using the ssh -v backup command: Authenticated to ([]:22) However, when launching duply backup routine, I see that the server is not recognized: The authenticity of host '[]:22' can't be established. SSH-ED25519 key fingerprint is c3:06:95:f8:5f:d3:76:7f:c6:9d:19:ef:e5:23:9a:14. Are you sure you want to continue connecting (yes/no)? Why is this happening? ---------- **Update** It seems that duply is computing the MD5 hash of the public key, while ssh the SHA256 one: in fact, as mentioned here , ssh-keygen -l -E md5 -f /etc/ssh/ssh_host_ed25519_key.pub returns the same hexadecimal stated above. Since they are two different hash of the same key, why a connection confirmation is still asked? Is it possible to oblige SSH to use only a single hash algorithm? **Further update:** ssh -o FingerprintHash=md5 -v backup does not require confirmation, so I suppose that the issue is limited to duply. Maybe, does it not refer to the user known_hosts file?

How can I restore some files from my duplicity backup excluding some directories/files ? Does --include --exclude work along with restore ?

No matter which command I try on this duply profile it always errors out. duply database status duply database bkp duply database purge They all return a trace similar to the following Start duply v1.11.3, time is 2017-11-30 12:20:12. Using profile '/etc/duply/database'. Using installed duplicity version 0.7.12, python 2.7.5, gpg 2.0.22 (Home: ~/.gnupg), awk 'GNU Awk 4.0.2', grep 'grep (GNU grep) 2.20', bash '4.2.46(1)-release (x86_64-redhat-linux-gnu)'. Checking TEMP_DIR '/srv/mysql/logs/duply_backup/duply_tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PURGE at 12:20:12.397 --- Using archive dir: /srv/mysql/logs/duply_backup/duply_cache/duply_database Using backup name: duply_database Import of duplicity.backends.acdclibackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.botobackend Succeeded Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.copycombackend Succeeded Import of duplicity.backends.dpbxbackend Failed: No module named dropbox Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Main action: remove-old ================================================================================ duplicity 0.7.12 (March 21, 2017) Args: /bin/duplicity remove-older-than 8W --archive-dir /srv/mysql/logs/duply_backup/duply_cache --name duply_database --no-encryption --verbosity 5 --full-if-older-than 4W --volsize 50 --include-filelist /etc/duply/database/include --exclude-filelist /etc/duply/database/exclude --rsync-options --rsh="ssh -oBatchMode=yes -i /root/.ssh/duplicity_scp.dsa" --copy-links rsync://root@10.21.230.69:22//backup-lun/duplicity//eventlogdb-core-01/database Linux eventlogdb-core-01.ecnza.net 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64 x86_64 /bin/python2 2.7.5 (default, Nov 6 2016, 00:28:07) [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] ================================================================================ Reading results of 'rsync -e 'ssh -p 22 -oBatchMode=yes ' --rsh="ssh -oBatchMode=yes -i /root/.ssh/duplicity_scp.dsa" root@10.21.230.69:/backup-lun/duplicity//eventlogdb-core-01/database/' Local and Remote metadata are synchronized, no sync needed. Reading results of 'rsync -e 'ssh -p 22 -oBatchMode=yes ' --rsh="ssh -oBatchMode=yes -i /root/.ssh/duplicity_scp.dsa" root@10.21.230.69:/backup-lun/duplicity//eventlogdb-core-01/database/' Processing local manifest /srv/mysql/logs/duply_backup/duply_cache/duply_database/duplicity-full.20171010T231503Z.manifest.part (634880) Using temporary directory /srv/mysql/logs/duply_backup/duply_tmp/duplicity-k1XfbU-tempdir Traceback (most recent call last): File "/bin/duplicity", line 1546, in with_tempdir(main) File "/bin/duplicity", line 1540, in with_tempdir fn() File "/bin/duplicity", line 1391, in main do_backup(action) File "/bin/duplicity", line 1416, in do_backup globals.archive_dir).set_values() File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 710, in set_values self.get_backup_chains(partials + backend_filename_list) File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 836, in get_backup_chains add_to_sets(f) File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 830, in add_to_sets if new_set.add_filename(filename): File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 101, in add_filename self.set_manifest(filename) File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 148, in set_manifest self.set_files_changed() File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 128, in set_files_changed mf = self.get_manifest() File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 250, in get_manifest return self.get_local_manifest() File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 224, in get_local_manifest return manifest.Manifest().from_string(manifest_buffer) File "/usr/lib64/python2.7/site-packages/duplicity/manifest.py", line 208, in from_string assert filecount == len(self.files_changed) AssertionError 12:20:14.362 Task 'PURGE' failed with exit code '30'. --- Finished state FAILED 'code 30' at 12:20:14.362 - Runtime 00:00:01.964 ---

I manage my backups with duply. Today I wanted to fetch some backuped files from an old machine that got lost on my current machine. Unfortunately I got the error that the storage was signed with another key than the key which was autoselected by duply: Autoset found secret key of first GPG_KEY entry 'B8C46F4D410B8E334BBA1ECA68D101873E261004' for signing. … Datenträger wurde von Schlüssel 68D101873E261004, anstatt von B8C46F4D410B8E334BBA1ECA68D101873E261004 unterschrieben (sorry for the 2. message in German but it says what I've just described) The curious thing is that I am convinced that it is the same key. First, I haven't changed any key duply copied into the profile folder when I created the profile. Second, the numbers of the signing key used by the storag (first key number) is just the last part of the key that was autoselected by duply from the profile folder. Thus, I do not understand what really is happening here. The keys which were stored by duply in the profile folder during profile generation look like this: $ ls gpgkey.B8C4_6F4D_410B_8E33_4BBA_1ECA_68D1_0187_3E26_1004.pub.asc gpgkey.B8C46F4D410B8E334BBA1ECA68D101873E261004.pub.asc gpgkey.B8C4_6F4D_410B_8E33_4BBA_1ECA_68D1_0187_3E26_1004.sec.asc gpgkey.B8C46F4D410B8E334BBA1ECA68D101873E261004.sec.asc which looks kind of redundant as well. In my duply profile config, it says GPG_KEY='B8C46F4D410B8E334BBA1ECA68D101873E261004' Another thing is, that I did not have any trouble when I used the setup the last time and since then I haven't changed anything manually

Is it possible to specify multiple source directories in a duply configuration file? If not is there any simple workaround?