[Duplicity-talk] More to "unable to connect" using duplicity 0.6.18...

[g d0b3rm4n]

Hi,

I have:

# duplicity -V
duplicity 0.6.18

It used to work for me on the CLI with new ssh backend, but not when
it was started via cron, via cron started I got:
BackendException: ssh connection to example.com:22 failed: Unknown
server example.com

so I narrowed it down to the following problem:

works:
# /usr/bin/duplicity full
--ssh-options=-oIdentityFile=/etc/backup/backup-ssh-key
--archive-dir=/data/arch --tempdir=/data/arch/tmp -v0 /root
scp://address@hidden/root


fails:
# HOME=/ /usr/bin/duplicity full
--ssh-options=-oIdentityFile=/etc/backup/backup-ssh-key
--archive-dir=/data/arch --tempdir=/data/arch/tmp -v0 /root
scp://address@hidden/root
BackendException: ssh connection to example.com:22 failed: Unknown
server example.com

I set the HOME env variable in cron to be /, so it seems (or I assume)
that the new ssh backend can't handle it if there is no
~/.ssh/known_hosts?

since it works if I do this:

# mkdir /.ssh
# cp ~/.ssh/known_hosts /.ssh/
# HOME=/ /usr/bin/duplicity full
--ssh-options=-oIdentityFile=/etc/backup/backup-ssh-key
--archive-dir=/data/arch --tempdir=/data/arch/tmp -v0 /root
scp://address@hidden/root


so the "Unknown server example.com" is misleading in this case!?

Can that be fixed or is it fixed in yesterdays release 0.6.19 with this:
- add missing_host_key prompt to new sshbackend similar to ssh procedure

br
Reto