Hi! On Tue, 2014-03-25 14:02:17 +0100, Jan-Benedict Glaw <[email protected]> wrote: > Out of curiosity, we added > --ssh-options=-oIdentityFile=/.../.ssh/id_rsa, but it seems (using > `duply') this strangely breaks GPG encryption when it's really used, > though it works initially when it tests to sign and encrypt with that > very key.
Actually, explicitely supplying the key file (instead of letting Paramiko find it automatically) seems to be a proper workaround for this issue. The GPG error seems to be unrelated and is also gone by now. As a workaround, this does the job. However, I'm not sure how to actually fix it, because there's so little debugging aid in Paramiko. Would have been nice to have lots of logging all over the place... If somebody who's deeper "into" the code wants to do in-depth debugging, I'll help! As another note, it *seems* that with Debian's current "unstable" version (1.10.1-1), I cannot trigger this bug on my desktop system, while it does trigger in Ubuntu's lucid version, 1.7.7.1-2ubuntu1. However, since this authentication error used to come and go for some extended period of time, this may or may not be a red herring. MfG, JBG -- Getslash GmbH, Bahnhofstraße 16, 59302 Oelde Tel: +49-2522-834349-5 Fax: +49-2522-834349-1 http://www.getslash.de Mobil: +49-152-33822499 Sitz der Gesellschaft: Oelde Handelsregister: Amtsgericht Münster, HRB 11911 Ust-Id-Nr.: DE 815060326 Geschäftsführung: Andre Peitz, Tobias Hanisch
signature.asc
Description: Digital signature
