micah a écrit (07 Nov 2005 23:13:33 +0100) : > 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.
Using keychain, one can share ssh-agent stored identities across
sessions : keychain stores (typically in ~/.keychain/${HOST}-sh)
working values for SSH_AUTH_SOCK and SSH_AGENT_PID environment
variables, which allows any shell program sourcing this file to use
the existing ssh-agent.
Ahmad, if we add support for keychain to backupninja, would you use
it?
Ninja-friends, what do you think of adding keychain support to
backupninja? I could do this one of these days, since I'm already
using keychain actually for other tasks.
Ciao,
--
intrigeri <[EMAIL PROTECTED]>
| gnupg key @ http://intrigeri.boum.org/intrigeri.asc
pgpRZo6xuVHNG.pgp
Description: PGP signature
