desktop-packages team mailing list archive

[Hendy Irawan <hendy@xxxxxxxxxxx>]

Still happens in Ubuntu 12.04 amd64 :

- duplicity 0.6.18-0ubuntu3.5
- python-paramiko 1.7.7.1-2ubuntu1

Workaround is to use rsync:// backend instead, which is (if available)
better than ssh/scp anyway.

"rsync:// should be able to resume transfer in the middle of the file, so if you are backing up large files over semi-reliable network, I would prefer that."
- Aleksandar Ivanisevic (http://serverfault.com/a/92621)

-- 
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-v01@xxxxxxxxxxx,ssh-dss-
  cert-v01@xxxxxxxxxxx,ssh-rsa-cert-v00@xxxxxxxxxxx,ssh-dss-
  cert-v00@xxxxxxxxxxx,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