On 2015-01-29 at 20:23:21, Alexander Zangerl wrote: > On Tue, 27 Jan 2015 15:10:34 +1300, Francois Marier writes: > >After upgrading from duplicity 0.6.24-2 to 0.7.01-1, my backups to an ssh > >host stopped working. > > i can't reproduce that; i've just used 0.7.01 sftp and scp backups > without major problems, using sftp://me@somehost/location as well as > scp://me@somehost/location.
This is what fails for me: duplicity cleanup --ssh-options="-oIdentityFile=id_rsa -oUserKnownHostsFile=known_hosts" --force scp://user@hostname/backup > >Now, if I try to run any of the duplicity commands, I get the following: > > > > BackendException: ssh connection to user@hostname:22 failed: No > > authenticatio > >n methods available > > looks like you need to set up ssh-agent and key auth, or > use --ssh-askpass or provide the password to duplicity via FTP_PASSWORD. > i've tested all three options and they work fine. I'm using a password-less key (as per the above command-line) so it's not a password or ssh-agent problem. > it looks as if the strictness of the auth handling changed somewhere > between 0.6.24 and 0.7.01, but the changelog doesn't show anything pertinent. There's also the possibility that it doesn't have anything to do with authentication. paramiko has a tendency to return misleading or unhelpful messages, unfortunately. Francois -- Francois Marier identi.ca/fmarier http://fmarier.org twitter.com/fmarier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
