On Tue, 18 Mar 2014 11:34:07 +0100, Frodo Larik writes: >A verbose trace of duplicity failing in action: ... >ssh: starting thread (client mode): 0x1e24590L >ssh: Connected (version 2.0, client OpenSSH_3.7.1p2) >ssh: kex algos:['diffie-hellman-group-exchange-sha1', 'diffie-hellman-group1-sh >a1'] server key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-cbc', '3des-cbc' >, 'blowfish-cbc'] server encrypt:['aes128-cbc', '3des-cbc', 'blowfish-cbc'] cli >ent mac:['hmac-md5', 'hmac-sha1', 'hmac-sha1-96'] server mac:['hmac-md5', 'hmac >-sha1', 'hmac-sha1-96'] client compress:['none'] server compress:['none'] clien >t lang:[''] server lang:[''] kex follows?False >ssh: Ciphers agreed: local®s128-cbc, remote®s128-cbc >ssh: using kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: loc >al aes128-cbc, remote aes128-cbc; mac: local hmac-sha1, remote hmac-sha1; compr >ession: local none, remote none >ssh: Switch to new keys ... >ssh: Trying discovered key ###################### in /root/.ssh/id_rsa >ssh: userauth is OK >ssh: Authentication (publickey) failed.
could you provide some info from the server side of one of those failing connections, ie. does your ssh server log anything useful on those instances? this looks like a bug in paramiko, the python ssh implementation that's used when you don't use the pexpect backend. regards az -- Alexander Zangerl + GPG Key 0xB963BD5F (or 0x42BD645D) + http://snafu.priv.at/ <html><form><input type crash></form></html> -- IE has a bad day.
signature.asc
Description: Digital Signature
