https://bugzilla.novell.com/show_bug.cgi?id=383353
User vuntz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=383353#c5
Vincent Untz changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vuntz@novell.com
AssignedTo|vuntz@novell.com |sndirsch@novell.com
Severity|Major |Normal
Component|GNOME |X.Org
QAContact|qa@suse.de |xorg-maintainer-bugs@forge.provo.novell.com
Summary|Forced to enter keyring password even though |/etc/X11/xdm/sys.xsession makes the pam-launched
|pam_gnome_keyring is used |gnome-keyring useless
--- Comment #5 from Vincent Untz 2008-05-13 15:52:43 MST ---
Okay, that's not a gnome-keyring issue, but a problem in how we handle
ssh-agent in /etc/X11/xdm/sys.xsession:
if test -S "$SSH_AUTH_SOCK" ; then
if test -n "$SSH_AGENT_PID" && checkproc -p $SSH_AGENT_PID $sshagent ;
then
export SSH_AGENT_PID SSH_AUTH_SOCK
else
rm -f "$SSH_AUTH_SOCK"
case "${SSH_AUTH_SOCK%/*}" in
/tmp/*) rm -rf "${SSH_AUTH_SOCK%/*}"
esac
unset SSH_AUTH_SOCK
fi
else
unset SSH_AUTH_SOCK
fi
That's assuming that the ssh agent is setting SSH_AGENT_PID and that the binary
is called ssh-agent, which is wrong for gnome-keyring. So the gnome-keyring
directory containing the socket is deleted.
A potential fix is explained in bug 389896. If this proposed fix is considered
too intrusive, a simpler fix might be to check for the existence of
GNOME_KEYRING_PID and gnome-keyring-daemon in addition to SSH_AGENT_PID and
ssh-agent.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.