Blog de Pierrick Le Gall

$ ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/home/pierrick/.ssh/id_dsa): /home/pierrick/.ssh/id_dsa2
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: /home/pierrick/.ssh/id_dsa2.pub.
Your identification has been saved in /home/pierrick/.ssh/id_dsa2.
Your public key has been saved in /home/pierrick/.ssh/id_dsa2.pub.

$ export EDITOR=vi; crontab -e
* * * * * ssh -i /home/pierrick/.ssh/id_dsa2 remote_user@remote_server 'echo $(date) >> /tmp/pierrick.log'

Trackbacks

Aucun trackback.

Les trackbacks pour ce billet sont fermés.

Commentaires

1. Le dimanche 9 septembre 2007 à 09:16, par Nicolas

An another better solution can be keychain. You can use a passphrase. keychain don't use the same solution than ssh-add to store the passphrase in a agent just for the current session. It stores the passphrase until the machine have to be rebooted.

2. Le jeudi 20 septembre 2007 à 10:35, par BooK

I have an agent running on my system, which I start with ssh-agent > ~/.ssh/agent. Making the agent known to your environment is as simple as typing . ~/.ssh/agent. This is a command one can type at the beginning of a cron command.

That way, you don't have to keep a private key without a password, and can still use it in a cron job.
You just have to make sure your agent is here after a reboot.

3. Le vendredi 21 septembre 2007 à 09:17, par Pierrick

BooK, alright to start an agent, but how do I add the key? "ssh-add" right? So I have to give the passphrase, right? So I have to right the clear passphrase somewhere, right? Where is security improvement?

Ajouter un commentaire

Les commentaires pour ce billet sont fermés.