Just upgraded from Snow Leopard to Lion, and my cron jobs that use ssh have stopped working. It appears that ssh-agent is no longer functioning as expected.
Here's a bowdlerized version of my called-from-cron script that worked great under Snow Leopard:
#!/bin/bash whoami # just to verify I'm running as myself, not root ssh-agent # just to see what it outputs eval `ssh-agent` ssh -vvv REMOTESERVER ls
When run from the command prompt, this script works as expected.
When run from cron, it doesn't work. The ssh-agent output looks normal:
SSH_AUTH_SOCK=/tmp/ssh-QRxPUMRxbu/agent.17147; export SSH_AUTH_SOCK; SSH_AGENT_PID=17148; export SSH_AGENT_PID; echo Agent pid 17148; Agent pid 17150
ssh -vvv output shows that it fails right when the private key should be read:
debug1: Server accepts key: pkalg ssh-dss blen 818 debug2: input_userauth_pk_ok: fp ... debug3: sign_and_send_pubkey: DSA ... debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> debug1: read_passphrase: can't open /dev/tty: Device not configured debug2: no passphrase given, try next key
In other words, it's expecting me to type in the passphrase for
~/.ssh/id_dsa, which of course doesn't work in cron jobs.
This all worked in Snow Leopard.
Note that I've got Keychain Access setup so that
ssh-add are allowed to read my passphrase for my
.ssh/id_dsa file - as a result I can SSH from a terminal prompt without ever having to enter my passphrase.
Is this issue that I need to run
ssh-add at some point in my login process? Running it from a standard bash prompt doesn't help the cron job out (although, oddly, it does prompt me for my passphrase ... which I would think isn't necessary b/c of the Keychain Access configuration).
NOTE 1 - before redirecting me - I'm aware there's a similar question here (
Mac OS X Lion and sshpass) but it's specifically about a program
sshpass that I don't use (although I believe that question would be answered by this one as well).
NOTE 2 - I can't create the "cron" tag b/c I lack sufficient rep. If someone with sufficient suction could do so & tag this question, that would be great.
NOTE 3 - I realize that passphrase-less SSH keys would solve my problem; however I'd prefer not to go this route.