root# emerge keychain
        

You could emerge gtk2-ssh-askpass if you want to graphically be prompted for your passphrase rather than via your shell.

You will need ssh keys that are used to allow ssh access in a secure fashion. You will want to pick a secure password for these things.

user# ssh-keygen -t rsa  # Follow the prompts
        

Now you need to create an authorized_keys file to be used on every computer you will want to ssh to

user# cd ~/.ssh
user# cat id_rsa.pub >> authorized_keys
        

Now copy this file to the machines you want access to

user# scp authorized_keys USER@HOST:.ssh/authorized_keys
        

Edit your ~/.bash_profile file and add the following near the top (I put this above the .bashrc include (the HOSTNAME below is literal by the way, cut and paste directly):

keychain ~/.ssh/id_rsa
. ~/.keychain/${HOSTNAME}-sh
        

If you happen to have a conditional statement in your .bashrc that checks for a non-interactive shell be sure to add keychain there too, being sure to use the --quiet switch:

# Test for an interactive shell.  There is no need to set anything
# past this point for scp and rcp, and it's important to refrain from
# outputting anything in those cases.
if [[ $- != *i* ]] ; then
    # Use keychain:
    keychain --quiet ~/.ssh/id_rsa
    . ~/.keychain/${HOSTNAME}-sh

    # Shell is non-interactive.  Be done now!
    return
fi
        

Now everytime you open a console up, you will see keychain startup. Note that the first time Keychain runs it will prompt for the password you used in your rsa key. Go ahead and close your gnome-terminal or whatever and open it back up again... and enter your password.

You should now be able to ssh to the particular host without having to enter a password. Nicely done!

If you use crontab, you will need to modify your scripts a bit in order for your ssh-agent to be available via crontab. There are probably several ways of doing this, and I really don't know if this is a security no-no, but the following works for me.

At the top of my personal bash files called by crontab, I source my profile like so:

#!/bin/bash
 
source ~/.bash_profile
# Doo something
        

I have not tested to see if the above will work if you reference a user's profile with root's crontab. but it works nicely for a normal user's crontab. Oh, and for those of you who get permission denied when trying to add a personal crontab, the key is to add the normal user to the cron group via gpasswd.

Good luck!