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.
(This is really annoying when you have a series of keys left unlocked unless you really need to connect to the server they were given to.)
Best regards Samuel --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-3-amd64 Debian Release: wheezy/sid 990 unstable ftp.fr.debian.org 500 testing ftp.fr.debian.org 500 stable ftp.fr.debian.org 1 experimental ftp.fr.debian.org --- Package information. --- Depends (Version) | Installed ========================================-+-=============== libc6 (>= 2.2.5) | librsync1 (>= 0.9.6) | python (>= 2.7) | python (<< 2.8) | python-gnupginterface (>= 0.3.2-9.1) | Recommends (Version) | Installed ==============================-+-=========== rsync | 3.0.9-3 python-paramiko | 1.7.7.1-3 Suggests (Version) | Installed ================================-+-=========== python-boto | 2.3.0-1 ncftp | python-pexpect (>= 2.3-1) | 2.4-1 python-cloudfiles | lftp | 4.3.8-1 python-gdata | 2.0.17-1 tahoe-lafs | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
