My client is Ubuntu 12.04, and the server is a FreeNAS 9.1.0 box. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/965017
Title: New SFTP backend uses outdated paramiko, breaks connection to server even with --use-scp Status in Duplicity - Bandwidth Efficient Encrypted Backup: Fix Released Status in “duplicity” package in Ubuntu: Fix Released Bug description: We recently tried updating from duplicity 0.6.17 to 0.6.18 on Gentoo. The SSH backend now makes uses of paramiko to establish a sftp connection. This is a problem because the paramiko library do not support ECDSA authentication, and because of that complains: BackendException: ssh connection to x failed: Unknown server x That is because there is no RSA or DSA key for server x in ~/.ssh/known_hosts. This shouldn't be a problem with --use-scp flag, however file sshbackend.py shows that it is indeed: check for self.client.connect happens before any check for globals.use_scp is done. We solved this temporarily via: ssh -o HostKeyAlgorithms='ssh-rsa-cert-...@openssh.com,ssh-dss- cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-dss- cert-...@openssh.com,ssh-rsa,ssh-dss' u@x Now it fails with another error: BackendException: ssh connection to x failed: No authentication methods available UPDATE: the documentation states that --use-scp allows duplicity to use scp. I had assumed it was in the way it used to be, but it seems not. I guess in the meantime the only option for us will be to downgrade duplicity in wait for a fix to this. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/965017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
