skarab13
December 15th, 2010, 12:46 PM
Hello,
If I launch "Terminal" from the Main Menu under Accessories, the environment includes the correct SSH_AUTH_SOCK variable:
declare -x SSH_AUTH_SOCK="/tmp/keyring-M9jm0W/ssh"
The same is true if I launch a terminal from the default keyboard shortcut ("Run a terminal"). However, if I create a custom keyboard shortcut (System->Preferences->Keyboard Shortcuts) which simply executes 'gnome-terminal' the SSH_AUTH_SOCK variable is quite different:
declare -x SSH_AUTH_SOCK="/tmp/ssh-QmxIEa1830/agent.1830"
This causes my shortcut to ssh to a remote host to prompt for a passphrase (thus defeating the purpose of gnome-keyring in this case).
Any ideas?
Thanks!
If I launch "Terminal" from the Main Menu under Accessories, the environment includes the correct SSH_AUTH_SOCK variable:
declare -x SSH_AUTH_SOCK="/tmp/keyring-M9jm0W/ssh"
The same is true if I launch a terminal from the default keyboard shortcut ("Run a terminal"). However, if I create a custom keyboard shortcut (System->Preferences->Keyboard Shortcuts) which simply executes 'gnome-terminal' the SSH_AUTH_SOCK variable is quite different:
declare -x SSH_AUTH_SOCK="/tmp/ssh-QmxIEa1830/agent.1830"
This causes my shortcut to ssh to a remote host to prompt for a passphrase (thus defeating the purpose of gnome-keyring in this case).
Any ideas?
Thanks!