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. What do you advise?
On Thu, Jan 19, 2012 at 9:59 AM, Alexander Zangerl <[email protected]> wrote: > On Wed, 18 Jan 2012 17:14:06 EST, "Jonathan E. Magen" writes: >> File "/usr/lib/python2.7/dist-packages/paramiko/hostkeys.py", line 155, in >>load >> e = HostKeyEntry.from_line(line) >> File "/usr/lib/python2.7/dist-packages/paramiko/hostkeys.py", line 67, in >>from_line >> key = RSAKey(data=base64.decodestring(key)) >> File "/usr/lib/python2.7/base64.py", line 321, in decodestring >> return binascii.a2b_base64(s) >>Error: Incorrect padding > > looks like a bug in paramiko: those last few lines indicate that paramiko > has a problem scanning your ~/.ssh/known_hosts file. > > could you please move that file out of the way temporarily and try again? > > if that works, then either your known_hosts file is corrupt > or suitably oddly formatted to confuse paramiko (maybe no trailing newline > on the last line of the file?). > > regards > az > > > -- > Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + > http://snafu.priv.at/ > ...the freezer is full, and the body in the bathtub is starting to decompose. > -- Tanuki on spammers > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iF4EAREIAAYFAk8YL/wACgkQ+bKELRvb2DxSHAEAjOrajWxBLN6BNlFAqHVcix0V > j0v3+fuYjhuqD+Y+y/MBAKqyOudMSk8fbUgVNCQ5ExU+dqzt4qt4izPzrxUOt807 > =ZMRL > -----END PGP SIGNATURE----- > -- Jonathan E. Magen 203-936-9665 http://www.yonkeltron.com GTALK: [email protected] http://twitter.com/yonkeltron ב"ה -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
