Re-use ssh-agent and/or gpg-agent between logins
keychain [ -hkQqV ] [ --clear --help --ignore-missing --noask --nocolor --nogui --nolock --quick --quiet --version ] [ --agents list ] [ --attempts num ] [ --dir dirname ] [ --host name ] [ --lockwait seconds ] [ --stop which ] [ --timeout minutes ] [ keys... ]
keychain is a manager for ssh-agent, typically run from ~/.bash_profile. It allows your shells and cron jobs to share a single ssh-agent process. By default, the ssh-agent started by keychain is long-running and will continue to run, even after you have logged out from the system. If you want to change this behavior, take a look at the --clear and --timeout options, described below.
When keychain is run, it checks for a running ssh-agent, otherwise it starts one. It saves the ssh-agent environment variables to ~/.keychain/${\s-1HOSTNAME\s0}-sh, so that subsequent logins and non-interactive shells such as cron jobs can source the file and make passwordless ssh connections. In addition, when keychain runs, it verifies that the key files specified on the command-line are known to ssh-agent, otherwise it loads them, prompting you for a password if necessary.
Keychain also supports gpg-agent in the same ways that ssh-agent is supported. By default keychain attempts to start all available agents but will fall back to only gpg-agent or only ssh-agent if either is unavailable. You can specifically limit keychain using the --agents option.
keychain supports most UNIX-like operating systems, including Cygwin. It works with Bourne-compatible, csh-compatible and fish shells.
Start the agents listed. By default keychain will build the list automatically based on the existence of ssh-agent and/or gpg-agent on the system. The list should be comma-separated, for example \*(L"gpg,ssh\*(R"
Try num times to add keys before giving up. The default is 1.
Delete all of ssh-agent's keys. Typically this is used in .bash_profile. The theory behind this is that keychain should assume that you are an intruder until proven otherwise. However, while this option increases security, it still allows your cron jobs to use your ssh keys when you're logged out.
Keys are subject to interactive confirmation by the \s-1SSH_ASKPASS\s0 program before being used for authentication. See the -c option for ssh-add\|(1).
Keychain will use dirname rather than $HOME/.keychain
Keychain will print lines to be evaluated in the shell on stdout. It respects the \s-1SHELL\s0 environment variable to determine if Bourne shell or C shell output is expected.
After parsing options, keychain will load additional environment settings from \*(L"filename\*(R". By default, if \*(L"--env\*(R" is not given, then keychain will attempt to load from ~/.keychain/[hostname]-env or alternatively ~/.keychain/env. The purpose of this file is to override settings such as \s-1PATH\s0, in case ssh is stored in a non-standard place.
Show help that looks remarkably like this man-page. As of 2.6.10, help is sent to stdout so it can be easily piped to a pager.
Set alternate hostname for creation of pidfiles
Don't warn if some keys on the command-line can't be found. This is useful for situations where you have a shared .bash_profile, but your keys might not be available on every machine where keychain is run.
Attempt to inherit agent variables from the environment. This can be useful in a variety of circumstances, for example when ssh-agent is started by gdm. The following values are valid for \*(L"which\*(R":
Inherit when a pid (e.g. \s-1SSH_AGENT_PID\s0) is set in the environment. This disallows inheriting a forwarded agent.
Inherit when a sock (e.g. \s-1SSH_AUTH_SOCK\s0) is set in the environment. This allows inheriting a forwarded agent.
Same as \*(L"local\*(R", but only inherit if keychain isn't already providing an agent.
Same as \*(L"any\*(R", but only inherit if keychain isn't already providing an agent.
By default, keychain-2.5.0 and later will behave as if \*(L"--inherit local-once\*(R" is specified. You should specify \*(L"--noinherit\*(R" if you want the older behavior.
How long to wait for the lock to become available. Defaults to 5 seconds. Specify a value of zero or more. If the lock cannot be acquired within the specified number of seconds, then this keychain process will forcefully acquire the lock.
This option tells keychain do everything it normally does (ensure ssh-agent is running, set up the ~/.keychain/[hostname]-{c}sh files) except that it will not prompt you to add any of the keys you specified if they haven't yet been added to ssh-agent.
Disable color hilighting for non ANSI-compatible terms.
Don't honor \s-1SSH_ASKPASS\s0, if it is set. This will cause ssh-add to prompt on the terminal instead of using a graphical program.
Don't inherit any agent processes, overriding the default \*(L"--inherit local-once\*(R"
Don't attempt to use a lockfile while manipulating files, pids and keys.
Kill currently running agent processes. The following values are valid for \*(L"which\*(R":
Kill all agent processes and quit keychain immediately. Prior to keychain-2.5.0, this was the behavior of the bare \*(L"--stop\*(R" option.
Kill agent processes other than the one keychain is providing. Prior to keychain-2.5.0, keychain would do this automatically. The new behavior requires that you specify it explicitly if you want it.
Kill keychain's agent processes, leaving other agents alone.
If an ssh-agent process is running then use it. Don't verify the list of keys, other than making sure it's non-empty. This option avoids locking when possible so that multiple terminals can be opened simultaneously without waiting on each other.
Only print messages in case of warning, error or required interactivity. As of version 2.6.10, this also suppresses \*(L"Identities added\*(R" messages for ssh-agent.
Set a timeout in minutes on your keys. This is conveyed to ssh-agent which does the actual timing out of keys since keychain doesn't run continuously.
Show version information.
This snippet should work in any shell to load two ssh keys and one gpg key:
eval `keychain --eval id_rsa id_dsa 0123ABCD`
If you have trouble with that in csh:
setenv SHELL /bin/csh eval `keychain --eval id_rsa id_dsa 0123ABCD`
This is equivalent for Bourne shells (including bash and zsh) but doesn't use keychain's --eval feature:
keychain id_rsa id_dsa 0123ABCD [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n` [ -f $HOME/.keychain/$HOSTNAME-sh ] && \ . $HOME/.keychain/$HOSTNAME-sh [ -f $HOME/.keychain/$HOSTNAME-sh-gpg ] && \ . $HOME/.keychain/$HOSTNAME-sh-gpg
This is equivalent for C shell (including tcsh):
keychain id_rsa id_dsa 0123ABCD host=`uname -n` if (-f $HOME/.keychain/$host-csh) then source $HOME/.keychain/$host-csh endif if (-f $HOME/.keychain/$host-csh-gpg) then source $HOME/.keychain/$host-csh-gpg endif
To load keychain variables from a script (for example from cron) and abort unless id_dsa is available:
# Load keychain variables and check for id_dsa [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n` . $HOME/.keychain/$HOSTNAME-sh 2>/dev/null ssh-add -l 2>/dev/null | grep -q id_dsa || exit 1
ssh-agent\|(1)
Keychain was created and is currently maintained by Daniel Robbins. If you need to report a bug or request an enhancement, please post to the funtoo-dev mailing list <http://groups.google.com/group/funtoo-dev>. For more information about keychain, please visit <http://www.funtoo.org>.