On Thu, 19 Jan 2012 10:03:31 EST, "Jonathan E. Magen" writes:
>That caused it to get past that error. 
>I can try to regenerate the
>known_hosts file but I doubt it has a corruption considering that I
>have never had any other issues with SSH or SSH-related tools and
>previous versions of duplicity functioned without issue. 

maybe not full-blown corruption but there's obviously something in that file
where ssh is fine, but where paramiko is pickier or not sufficiently
flexible or something like that.

>What do you advise?

if you can supply the problematic known_hosts file i'll reassign the bug
to paramiko; without that file it'd be extremely hard/impossible to pinpoint
the problem...

regards
az


-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
"When the revolution comes, we'll need a longer wall." -- Tom De Mulder

Attachment: signature.asc
Description: Digital Signature

Reply via email to