Re: [Duplicity-talk] sshbackend tops working (?) after update from 0.6.13 to 0.6.14

[Chris Poole]

2011/7/1 Kenneth Loafman <address@hidden>:
> I looked at the changes made in sshbackend.py between .13 and .14.  Nothing
> there that would cause a password issue.  Did you change any other file?

I agree, I looked too and didn't see anything. One of the changes must be
causing an issue though. I didn't change any other file. I simply pulled
sshbackend.py from the .13 tarball and added it to the .14 install. I also
removed the old sshbackend.pyc too, as I couldn't remember if python would check
times and load the .py file or not.

> Also, could you verify that you are indeed using the correct key id when
> running the two versions?

Yes, the key ID is correct. As I say I simply ran the .13 command, then changed
nothing but s/.13/.14/ and I got the error.

********

I've just tried the rsync backend, literally s_scp://_rsync://_, and it worked
fine. Of course, rsync is running over ssh too ("rsync -e 'ssh
-oBatchMode=yes'") is appearing in the output of duplicity. The server itself
only allows rsync over ssh, and I've verified this with packet inspection with
Wireshark, and the fact that the only password I've entered is the password to
unlock my ssh key.


Chris