This issue only started to bite me after upgrading to intrepid.
I note:
1. Turning off the ssh component of gnome-keyring under gconf (set /apps/gnome-keyring/daemon-components/ssh to false) no longer seems to work (I guess this is what has changed with intrepid).
2. Commenting out the line:
session optional pam_gnome_keyring.so auto_start
in /etc/pam.d/gdm _does_ work for me. This stops gnome-keyring from hijacking SSH_AUTH_SOCK and involving itself irritatingly in the affairs of ssh. However, I have no actual use for gnome-keyring and so cannot say if my fix breaks something for those that do. YMMV.
This issue only started to bite me after upgrading to intrepid.
I note:
1. Turning off the ssh component of gnome-keyring under gconf (set /apps/gnome- keyring/ daemon- components/ ssh to false) no longer seems to work (I guess this is what has changed with intrepid).
2. Commenting out the line:
session optional pam_gnome_ keyring. so auto_start
in /etc/pam.d/gdm _does_ work for me. This stops gnome-keyring from hijacking SSH_AUTH_SOCK and involving itself irritatingly in the affairs of ssh. However, I have no actual use for gnome-keyring and so cannot say if my fix breaks something for those that do. YMMV.
---Fran