Bug#337954: Remote rdiff: Can't connect, test succeeds

[Ahmad Khayyat]

1. That was my substituation.. consider those as variables. 2. Is there any means by which I can provide the passphrase to the scheduled backups? It seems that thay do not run in the current logged-in session, otherwise they could have used the session's ssh agent. micah wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ahmad Khayyat wrote: Package: backupninja Version: 0.9-1 backupninja -t -n succeeds, but scheduled backups don's. They produce the message: *failed* -- /etc/backup.d/90.rdiff == fatal errors from /etc/backup.d/90.rdiff == Fatal: Can't connect to <dest-host> as <dest-user>. Does the error really say <dest-host> as <dest-user>, or was this a substitution that you did? I noticed that the helper script uses dsa while I'm using rsa. Anyway, I can ssh without a password and backupninja -n completes the backup successfully. Note that I have a passphrase for my keys but I'm using an agent (ssh-add) so that I can ssh without any prompts or passwords. I don't want to have an empty passphrase. If you have a passphrase on your key, then scheduled backups are going to somehow need to get that passphrase from you during the backups... micah -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDb4Wz9n4qXRzy1ioRAvy6AJ9asqO5WXJdSYRx0n1sI8pM2ct+RwCgnZ4x adTxTs97pnZPz/2t/9XtrJg= =4gzg -----END PGP SIGNATURE-----