-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ahmad Khayyat wrote: > 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. I've only done it via ssh-keys and passwordless logins to unpriviledged remote users. The only way a cronjob could use your ssh-agent is if it was launched from a shell that was created after the agent was launched. Cron stuff generally runs as root however, so you would have to have a ssh-agent for root and restart crond after you've ran ssh-agent to get it to work, but this is really weird. Really, this is the point of public keys... create an unpriviledged user on the backup machine that can only execute the rdiff-backup commands via ssh authorized_keys and it should be fine. micah -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDb9GN9n4qXRzy1ioRAiZxAJwN8/cHzaM9ik0tD4O6BvX/WWzIhQCgkZ8D FOrGkQJhKCFnk4sSVV/cFHs= =05GX -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
