Ssh-add does not stay, er, added...

Question

I'm troubleshooting an installation of SSH-Keys. I've successfully installed this with another user. After considerable effort can not discover why the two accounts do not behave the same. One account asks for the passphrase on login, and the other doesn't. Both accounts have the single line ssh-add in ~/.bash_profile.
Where does ssh-add store the added key for each user? Can I inspect this to discover the problem?
[xtian@frylock .ssh]$ ssh-add xtian_frylock-id_rsa
Enter passphrase for xtian_frylock-id_rsa:
Identity added: xtian_frylock-id_rsa (xtian_frylock-id_rsa)
[xtian@frylock .ssh]$ ssh-add -L
ssh-rsa AAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xtian_frylock-id_rsa
Logout and log back in to find,
[xtian@frylock ~]$ ssh-add -L
The agent has no identities.
Last edited by xtian (2013-10-23 23:41:31)

Answer 1

Ok. Here's the output from the working root account:
[root@frylock ~]# printenv | grep -i ssh
SSH_AGENT_PID=701
SSH_AUTH_SOCK=/tmp/ssh-0HKTJiMZQ6ob/agent.700
And here's the output from the non-working user account:
[xtian@frylock ~]$ printenv | grep -i ssh
SSH_AGENT_PID=836
SSH_AUTH_SOCK=/tmp/ssh-q6eu9w7ofDc3/agent.835
Now, I don't launch ssh-agent in .bash_profile. Before I tried to configure gpg-agent and, as near as I can recall, I used the same configuration when I fell back to using ssh-agent. Which is to say I put the eval line in a separate file in /etc/profile.d:
[xtian@frylock ~]$ cat /etc/profile.d/ssh-agent.sh
#!/bin/bash
eval $(ssh-agent)
Where are the ssh-agent environmental variables set? Not in /tmp
Last edited by xtian (2013-10-25 22:19:54)