On Mon, 24 Sep 2012 15:18:44 +0200, Samuel Hym writes: >Package: duplicity >Version: 0.6.18-3 >Severity: normal > >Launching duplicity with an ssh backend asks for all the ssh keys in >~/.ssh/ to be unlocked (presumably in case one of them would be useful >to the connection we try to establish). >I could not find any way to deactivate this probing (as with >IdentitiesOnly in ssh configuration, for instance) beside moving away >the keys.
0.6.19 and newer contain two ssh backends, the new default paramiko (which
doesn't support the full set of ssh options but is faster and cleaner),
and ssh-via-pexpect, which was the only backend until 0.6.17 when paramiko
was added.
the pexpect backend supports all ssh options - after all it runs ssh/scp/sftp
on your behalf.
duplicity full ...otheroptions... --ssh-backend pexpect
--ssh-options="-oidentityfile=thiskeyonly.priv -oIdentitiesOnly=yes"
...somesource ...sometargeturl
works fine and doesn't touch the ssh agent - excpet that i had made a
packaging mistake in 0.6.20++ which kept the old pexpect backend
from loading.
this is fixed in version 0.6.23-1 which will hit the archives within
the next two hours.
regards
az
--
Alexander Zangerl + GPG Key 0xB963BD5F (or 0x42BD645D) + http://snafu.priv.at/
"Alas I've yet to find a gig which offers "control of Orbital Anvil
Delivery System at weekends" as a fringe-benefit." -- Tanuki
signature.asc
Description: Digital Signature
