]> git.wh0rd.org - home.git/blame - .profile.d/keychain.sh
cros-board: update
[home.git] / .profile.d / keychain.sh
CommitLineData
d64d0217
MF
1# If an auth sock is already set & available, use it.
2# This way ssh agent forwarding still works.
5176a509
MF
3if type keychain >/dev/null 2>&1 ; then
4 if [ ! -S "${SSH_AUTH_SOCK}" ] ; then
d64d0217
MF
5 : ${HOSTNAME:=$(hostname)}
6 [ -e ~/.keychain/${HOSTNAME}-sh ] && . ~/.keychain/${HOSTNAME}-sh
5176a509
MF
7 fi
8 if [ -z "${GPG_AGENT_INFO}" ] ; then
9 : ${HOSTNAME:=$(hostname)}
d64d0217
MF
10 [ -e ~/.keychain/${HOSTNAME}-sh-gpg ] && . ~/.keychain/${HOSTNAME}-sh-gpg
11 fi
1afdf944 12fi
007ad6b8
MF
13
14# The agent might try to spawn pinentry on the tty it started
15# on instead of the tty gpg is now running on.
16export GPG_TTY="$(tty)"